התחל

חפש סקריפטים עבור "the script"

BUY/SELL + ADVANCE DECLINEThis script is a custom trading view indicator that helps to identify potential buy and sell signals based on the RSI (Relative Strength Index) and SMA (Simple Moving Average) indicators. The script also identifies potential reversals using a combination of RSI and price action. It plots buy, sell, and reversal signals on the chart along with an SMA line. Additionally, it provides alerts based on the buy, sell, and reversal conditions. Changes made to the original script: Fixed the undeclared identifier 'c' error by calculating the difference between the current closing price and the previous closing price: c = close - close . Added an "ADD Value Floating Label" to the chart. The label shows the difference between the current and previous closing prices (ADD value) along with a "Bullish" or "Bearish" indicator based on the value of 'c'. The label is positioned at the top right of the visible chart area and remains static. Here's a summary of the major components of the script: Input settings: Define the input parameters for RSI and SMA. Calculation of RSI and SMA: Compute the RSI and SMA values based on the input parameters. Color definitions: Define colors for different conditions and levels. Condition definitions: Define various conditions for buy, sell, reversal, and other criteria. Buy and sell conditions: Determine buy and sell signals based on RSI, SMA, and price action. Reversal conditions: Identify potential reversals using RSI and price action. Plot signals: Display buy, sell, and reversal signals on the chart. Bar colors: Color the bars based on the identified signals. Plot SMA: Display the SMA line on the chart. Alert conditions: Set up alerts for buy, sell, and reversal conditions. ADD Value Floating Label: Add a label to the chart showing the ADD value and a "Bullish" or "Bearish" indicator.
אינדיקטור Pine Script®
מאת ‎ChaseSpeegle‎
15
Divergences in 52 Week Moving Averages, Adjusted and SmoothedThis script description is intended to be holistic and comprehensive for the understanding of the interested parties who view the script. Following the PineCoders suggestions, I have provided detailed breakdowns both within the code and in the description immediately below: ► Description This description is intended to be detailed and meaningful, conveying the understanding of the script’s intention to the user: The theory: Divergences and extreme readings in 52-Week highs on major indexes can provide a view into a potential pending move in the opposite direction of how the market has been trending. By comparing the 52-Week Hi/Lo indices and applying an Exponential Moving Average (EMA), we can assess how extreme a move is from the average. If the move provides an extreme reading, it would potentially be beneficial to “fade” the move (take a position in the opposing direction). The intention: The intentionality of this script is to provide a visualization of when the highly-probable opportunity to fade over a multi-day or multi-week period arises. In addition to this, based on backtesting prior moves and reading the various levels of significant reversals, three tiers: “Standard”, “Sensitive”, and “Highly Sensitive” have been applied, the user can choose which sensitivity level they would like to see, there are far less false positives on the Standard and Sensitive settings, while Highly Sensitive often signals multiple times with the move coming a few days later. The application: The settings allow the user to customize their sensitivity to the fade signals, with the ability to customize the visual that shows up as well. For higher-highs that are fade-worthy, the signal will appear on the top of the candle, for lower-lows that are fade-worthy, the signal will appear on the bottom of the candle. The users risk criteria should be the primary driver of the entry/exit, although when backtesting it appears that the significant move is typically completed within a 2-4 week period at max and 3-5 day period at minimum. A personal note: I am a futures trader intraday but would very strongly caution users when using this strategy with futures (unless their risk tolerance is higher than most). The most beneficial strategy when fading moves would be to enter in tranches, starting at the first signal and adding on any pullback (as long as the pullback is not below the initial entry point). 1-6 Week Date-To-Expiry options would be the primary method for applying this strategy. I would also like to add that SPY/SPX options (SPDR S&P 500 ETF Trust / CBOE S&P 500 Index) are the most liquid options that could be applied in this strategy. ► Description (additional) With the understanding that few users can read pinescript (Pine), the description above contains all of the necessary information that is necessary for a user to understand the intention for script utilization. For those who do understand Pine, the code is commented in each section in order to provide an understanding of the underlying functions, calculations, and thought process that went on during the writing of the script. ► Description (additional) This script’s description contains no delegations, all aspects of the script as well as the initial idea behind it are contained in the description above, which is self-contained in it’s entirety with a clear and defined purpose that is written with the intent to holistically capture the intent of the potential use for this indicator. ► General House Rule #2 This script and the description (as well as my profile) contain no links or associations to promotion of any kind, I am not a business, I am not an individual that will in any way make money from this script or the promotion of another person, idea, company, entity, or legal persons (foreign or domestic). ► Originality and usefulness This is an original and custom script (and idea) that is not a rehashing or a copy of any code from any other programmers in the tradingview community.
אינדיקטור Pine Script®
מאת ‎blueberryjones‎
Crypto Uptrend Script + Pullback//Volume CandlesDescription: his is an adaption of my Pullback candle - This works on all timeframes and Markets (Forex//Stocks//) Crypto Uptrend Script with Pullback Candle allows traders to get into a trend when the price is at end of a pullback and entering a balance phase in the market (works on all markets). The use of Moving averages to help identify a Trends and the use of Key levels to help traders be aware of where strong areas are in the market. This script can work really well in Crypto Bull Runs when used on HTF and with confluences The script has key support and resistance zones which are made up of quarterly data. Price reacts to these areas but patience is required as price will take time to come into these areas I have updated the Pullback Candle with the use of Volume to filter out the weak Pullback Candles - There are new candles to the script. The First candle is the Bullish Volume Candle - This candle is set to a multiplier of 2x with a crossover of 50/100 on Volume - this then will paint a purple candle. Uses of the Bullish Volume Candle: Breakthrough of key areas // special chart patterns Rejection of key areas End of a impulse wave (Profit Takers) The second candle is a Hammer - I prefer using the Hammers on Higher Timeframes however they do work on all timeframes. . The third candle is a Exhaustion of impulse downward move. Uses of this candle - can denote a new trend but has to be with confluence to a demand area // support area or with any use of technical analysis - using this alone is not advised The fourth candle is a indecision candle in the shape of a Doji - this candle can help identify if the trend is in a continuation or a reversal This script can work really well in Crypto Bull Runs Disclaimer: There will be Pullbacks with High Volume (Breakouts) and not go the way as intended but this script is to allow traders to get into trends at good price levels. The script can paint signals in areas where price is too expensive so please do your own due diligence on the markets as this script is to help get into good areas of price Please leave a thumbs up if you like this script and message me for information on how to use the script.
אינדיקטור Pine Script®
מאת ‎LuxTradeVenture‎
9
Weis V5 zigzag jayySomehow, I deleted version 5 of the zigzag script. Same name. I have added some older notes describing how the Weis Wave works. I have also changed the date restriction that stopped the script from working after Dec 31, 2022. What you see here is the Weis zigzag wave plotted directly on the price chart. This script is the companion to the Weis cumulative wave volume script. What is a Weis wave? David Weis has been recognized as a Wyckoff method analyst he has written two books one of which, Trades About to Happen, describes the evolution of the now-popular Weis wave. The method employed by Weis is to identify waves of price action and to compare the strength of the waves on characteristics of wave strength. Chief among the characteristics of strength is the cumulative volume of the wave. There are other markers that Weis uses as well for example how the actual price difference between the start of the Weis wave from start to finish. Weis also uses time, particularly when using a Renko chart David Weis did a futures io video which is a popular source of information about his method. (Search David Weis and futures.io. I strongly suggest you also read “Trades About to Happen” by David Weis. This will get you up and running more quickly when studying charts. However, you should choose the Traditional method to be true to David Weis technique as described in his book "Trades About to Happen" and in the Futures IO Webcast featuring David Weis . The Weis pip zigzag wave shows how far in terms of bar close price a Weis wave has traveled through the duration of a Weis wave. The Weis zigzag wave is used in combination with the Weis cumulative volume wave. The two waves should be set to the same "wave size". To use this script, you must set the wave size: Using the traditional Weis method simply enter the desired wave size in the box "How should wave size be calculated", in this example I am using a traditional wave size of .25. Each wave for each security and each timeframe requires its own wave size. Although not the traditional method devised by David Weis a more automatic way to set wave size would be to use Average True Range (ATR). Using ATR is not the true Weis method but it does give you similar waves and, importantly, without the hassle described above. Once the Weis wave size is set then the zigzag wave will be shown with volume. Because Weis used the closing price of a wave to define waves a line Bar highs and bar lows are not captured by the Weis Wave. The default script setting is now cumulative volume waves using an ATR of 7 and a multiplication factor of .5. To display volume in a way that does not crowd out neighbouring volumes Weis displayed volume as a maximum of 3 digits (usually). Consider two Weis Wave volumes 176,895,570 and 2,654,763,889. To display wave volume as three digits it is necessary to take a number such as 176,895,570 and truncate it. 176,895,570 can be represented as 177 X 10 to the power of 6. The number displayed must also be relative to other numbers in the field. If the highest volume on the page is: 2,654,763,889 and with only three numbers available to display the result the value shown must be 265 (265 X 10 to the power of 7). Since 176,895,570 is an order of magnitude smaller than 2,654,763,889 therefore 175,895,570 must be shown as 18 instead of 177. In this way, the relative magnitudes of the two volumes can be understood. All numbers in the field of view must be truncated by the same order of magnitude to make the relative volumes understandable. The script attempts to calculate the order of magnitude value automatically. If you see a red number in the field of view it means the script has failed to do the calculation automatically and you should use the manual method – use the dialogue box “Calculate truncated wave value automatically or manually”. Scroll down from the automatic method and select manual. Once "manual" is selected the values displayed become the power values or multipliers for each wave. Using the manual method you will select a “Multiplier” in the next dialogue box. Scan the field and select the largest value in the field of view (visible chart) is the multiplier of interest. If you select a lower number than the maximum value will see at least one red “up”. If you are too high you will see at least one red “down”. Scroll in the direction recommended or the values on the screen will be totally incorrect. With volume truncated to the highest order values, the eye can quickly get a feel for relative volumes. It also reduces the crowding and overlapping of values on the screen. You can opt to show the full volume to help get a sense of the magnitude of the true volumes. How does the script determine if a Weis wave is continuing to grow or not? The script evaluates the closing price of each new bar relative to the "Weis wave size". Suppose the current bar closes at a new low close, within the current down wave, at $30.00. If the Weis wave size is $0.10 then the algorithm will remember the $30.00 close and compare it to the close of the next bar. If the bar close price does not close equal to or lower than $30.00 or close equal to or higher than $30.10 then the wave is still a down wave with a current low of $30.00. This is true even if the bar low is less than $30.00 or the bar high is greater than 30.10 – only the bar’s closing price matters. If a bar's closing price climbs back up to a close of $30.11 then because the closing price has moved more than $0.10 (the Weis wave size) then that is a wave reversal with a new up-trending wave. In the above example if there was currently a downward trending wave and the bar closes were as follows $30.00, $30.09, $30.01, $30.05, $30.10 The wave direction would continue to stay downward trending until the close of $30.10 was achieved. As such $30.00 would be the low and the following closes $30.09, $30.01, $30.05 would be allocated to the new upward-trending wave. If however There was a series of bar closes like this $30.00, $30.09, $30.01, $30.05, $29.99 since none of the closes was equal to above the 10-cent reversal target of $30.10 but instead, a new Weis wave low was achieved ($29.99). As such the closes of $30.09, $30.01, $30.05 would all be attributed to the continued down-trending wave with a current low of $29.99, even though the closing price for the interim bars was above $30.00. Now that the Weis Wave low is now 429.99 then, in order to reverse this continued downtrend price will need to close at or above $30.09 on subsequent bar closes assuming now new low bar close is achieved. With large wave sizes, wave direction can be in limbo for many bars before a close either renews wave direction or reverses it and confirms wave direction as either a reversal or a continuation. On the zig-zag, a wave line and its volume will not be "printed" until a wave reversal is confirmed. The wave attribution is similar when using other methods to define wave size. If ATR is used for wave size instead of a traditional wave constant size such as $0.10 or $2 or 2000 pips or ... then the wave size is calculated based on current ATR instead of the Weis wave constant (Traditional selected value). I have the option to display pseudo-Ord volume. In truth, Ord used more traditional zig-zag pivots of bar highs and lows. Waves using closes as pivots can have some significant differences. This difference can be lessened by using smaller time frames and larger wave sizes. There are other options such to display the delta price or pip size of a Weis Wave, the number of bars in a wave, and a few other options.
אינדיקטור Pine Script®
מאת ‎jayy‎
30
DMI StrategyThis strategy is based on DMI indicator. It helps me to identify base or top of the script. I mostly use this script to trade in Nifty bank options, even when the signal comes in nifty . It can be used to trade in other scripts as well. Pivot points can also be used to take entry. Long entry is taken when DI+(11) goes below 10 and DI-(11) goes above 40 , whereas short entry is taken when DI-(11) goes below 10 and DI+(11) goes above 40. For bank nifty , I take the trade in the strike price for which the current premium is nearby 300, with the SL of 20%. If premium goes below 10% I buy one more lot to average, but exit if the premium goes below 20% of the first entry. If the trade moves in the correct direction, we need to start trailing our stoploss or exit at the pre-defined target. As this a strategy, there is one problem. While we are in the phase of "long", if again the "long" phase comes, it will not be shown on chart until a "short" phase has come, and vice versa. This has been resolved by creating an indicator instead of strategy with the name of "DMI Buy-sell on chart". Please go through that to get more entry points. Please have a look at strategy tester to back test
אסטרטגיית Pine Script®
מאת ‎email_analysts‎
3LS | 3 Line Strike Strategy [Kintsugi Trading]What is the 3LS | 3 Line Strike Strategy? Incorporating the 3 Line Strike candlestick pattern into our strategy was inspired by Arty at The Moving Average and the amazing traders at TheTrdFloor . The Three Line Strike is a trend continuation candlestick pattern consisting of four candles. Depending on their heights and collocation, a bullish or a bearish trend continuation can be predicted. In a symphony of trend analysis, price action, and volume we can find and place high-probability trades with the 3LS Strategy. How to use it! ----- First, start by choosing a Stop-Loss Strategy, Stop PIP Size, and Risk/Reward Ratio ----- - Stop-Loss Strategy Fixed PIP Size – This uses the top/bottom of the indicator candle and places a TP based on the chosen Risk:Reward ratio. ATR Trail (No set Target Profit, only uses ATR Stop) ATR Trail-Stop (Has set Target Profit, however, stop is based on ATR inputs) **If you choose an ATR Stop-Loss Strategy - input the desired ATR period and Multiple you would like the stop to be calculated at** **ATR Stop-Loss Strategies have a unique alert setup for Auto-Trading. See Auto-Trading Section** - Risk/Reward Ratio = If you have a .5 risk/reward, it means you are risking $100 to make $50. - Additional Stop PIP Size = Number of PIPs over the default stop location of the top or bottom of the indicator candle. ----- Next, we set the Session Filter ----- Set the Timezone and Trade Session you desire. If no specific session is desired, simply set the Trade Session to 00:00 - 00:00. ----- Next, we set the Moving Average Cloud Fill ----- Enter the Fast and Slow Moving Average Length used to calculate trend direction: MA Period Fast MA Period Slow These inputs will determine whether the strategy looks for Long or Short positions. ----- Next, we set the VSA – Volume Spread Analysis Settings ----- Check the box to show the indicator at the bottom of the chart if desired. This is just a different visual output of the VSA | Volume Spread Analysis indicator available for free under the community indicators tab. You can add that indicator to your chart and see the same output in candle format. In combination with the Moving Average Cloud, the Volume Spread Analysis will help us determine when to take a trade and in what direction. The strategy is essentially looking for small reversals going against the overall trend and placing a trade once that reversal ends and the price moves back in the direction of the overall trend. The 3LS Strategy utilizes confirmation between trend, volume, and price action to place high probability trades. The VSA is completely customizable by: Moving Average Length MA-1 Multiplier MA-2 Multiplier MA-3 Multiplier Check out the VSA | Volume Spread Analysis indicator in the community scripts section under the indicators tab to use this awesome resource on other strategies. ----- Next, we have the option to view the automated KT Bull/Bear Signals ----- Check the boxes to show the buy-sell signal on the chart if desired. ----- Next, we set the risk we want to use if Auto Trading the strategy ----- I always suggest using no more than 1-3% of your total account balance per trade. Remember, if you have multiple strategies triggering per day with each using 1%, the total percent at risk will be much larger. For Example – if you have 10 strategies each risking 1% your total risk is 10% of your account, not 1%! Be mindful to only use 1-3% of your total account balance across all strategies, not just each individual one. ----- Finally, we backtest our ideas ----- After using the 'Strategy Tester' tab on TradingView to thoroughly backtest your predictions you are ready to take it to the next level - Automated Trading! This was my whole reason for creating the script. If you work a full-time job, live in a time zone that is hard to trade, or just don't have the patience, this will be a game-changer for you as it was for me. Auto-Trading When it comes to auto-trading this strategy I have included two options in the script that utilize the alert messages generated by TradingView. *Note: Please trade on a demo account until you feel comfortable enough to use real money, and then please stick to 1%-2% of your total account value in risk per trade.* AutoView PineConnector **ATR Auto-Trading Alert Setup** How to create alerts on 3 Line Strike Strategy For Trailing Stops: 1) Adjust autoview/pineconnector settings 2) Click "add alert" 3) Select "Condition" = Strategy Name 4) Select "Order Fills Only" from the drop-down 3) Remove template message text from "message" box and place the exact text. '{{strategy.order.alert_message}}' 4) Click "create" For Fixed Pip Stop: 1) Adjust autoview/pineconnector settings 2) Click "add alert" 3) Select "Condition" = Strategy Name 4) Select "alert() function calls only" 5) I like to title my Alert Name the same thing I named it as an Indicator Template to keep track Good luck with your trading!
אסטרטגיית Pine Script®
מאת ‎KintsugiTrading‎
7
Buy/Sell on the levelsThis script is generally My describe is: There are a lot of levels we would like to buy some crypto. When the price has crossed the level-line - we buy, but only if we have the permission in array(2) When we have bought the crypto - we lose the permission for buy for now(till we will sell it on the next higher level) When we sell some crypto(on the buying level + 1) we have the permission again. There also are 2 protect indicators. We can buy if these indicators both green only(super trend and PIVOT ) Jun 12 Release Notes: Hello there, Uncomment this section before use for real trade: if array.get(price_to_sellBue, i) >= open and array.get(price_to_sellBue, i) <= close// and //direction < 0 and permission_for_buy != 0 Here is my script. In general - this is incredible simple script to use and understand. First of all You can see this script working with only long orders, it means we going to get money if crypto grows only. Short orders we need to close the position on time. In this script we buy crypto and sell with step 1% upper. You can simply change the step by changing the price arrays. Please note, if You want to see where the levels of this script is You Have to copy the next my indicator called LEVEL 1% In general - if the price has across the price-level we buy some crypto and loose permission for buying for this level till we sell some crypto. There is ''count_of_orders" array field with value 2. When we bought some crypto the value turns to 0. 0 means not allowed to by on this level!!! The script buy if the bar is green only(last tick). The script check every level(those we can see in "price_to_sellBue" array). If the price across one of them - full script runs. After buying(if it possible) we check is there any crypto for sell on the level. We check all levels below actual level( of actual level - ''i'' than we check all levels from 0 to i-1). If there is any order that has value 0 in count of orders and index <= i-1 - we count it to var SELL amount and in the end of loop sell all of it. Pay attention - it sells only if price across the level with red bar AND HAS ORDERS TO SELL WHICH WAS BOUGHT BELOW!!! In Strategy tester it shows not-profitables orders sometimes, because if You have old Long position - it sells it first. First in - first out. If the price goes down for a long time and You sell after 5 buys You sell the first of it with the highest value. There is 2 protection from horrible buying in this strategy. The first one - Supertrend. If the supertrend is red - there is no permission for buy. The second one - something between PIVOT and supertrend but with switcher. If the price across last minimum - switcher is red - no permission for buy and the actual price becomes last minimum . The last maximum calculated for last 100 bars. When the price across last maximum - switcher is green, we can buy. The last minimum calculation for last 100 bars, last maximum is actual price. This two protections will save You from buying if price get crash down. Enjoy my script. Should You need the code or explanation, You have any ideas how to improve this crypt, contact me. Vladyslav. Jun 12 Release Notes: Here has been uncommented the protection for buy in case of price get down. 5 hours ago Release Notes: Changed rages up to actual price to make it work
אסטרטגיית Pine Script®
מאת ‎Arivadis‎
2
CVD - Cumulative Volume Delta Candles█   OVERVIEW This indicator displays cumulative ​volume delta in candle form. It uses intrabar information to obtain more precise ​volume delta information than methods using only the chart's timeframe. █   CONCEPTS Bar polarity By bar polarity , we mean the direction of a bar, which is determined by looking at the bar's close vs its open . Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 bars at the lower timeframe of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This script uses a ​LTF to access intrabars. The lower the ​LTF, the more intrabars are analyzed, but the less chart bars can display ​CVD information because there is a limit to the total number of intrabars that can be analyzed. Volume delta The ​volume delta concept divides a bar's ​volume in "up" and "down" ​volumes. The delta is calculated by subtracting down ​volume from up ​volume. Many calculation techniques exist to isolate up and down ​volume within a bar. The simplest techniques use the polarity of interbar price changes to assign their ​volume to up or down slots, e.g., On Balance Volume or the Klinger Oscillator . Others such as Chaikin Money Flow use assumptions based on a bar's OHLC values. The most precise calculation method uses tick data and assigns the ​volume of each tick to the up or down slot depending on whether the transaction occurs at the bid or ask price. While this technique is ideal, it requires huge amounts of data on historical bars, which usually limits the historical depth of charts and the number of symbols for which tick data is available. This indicator uses intrabar analysis to achieve a compromise between the simplest and most precise methods of calculating ​volume delta. In the context where historical tick data is not yet available on TradingView, intrabar analysis is the most precise technique to calculate ​volume delta on historical bars on our charts. Our Volume Profile indicators use it. Other ​volume delta indicators in our Community Scripts such as the Realtime 5D Profile use realtime chart updates to achieve more precise ​volume delta calculations, but that method cannot be used on historical bars, so those indicators only work in real time. This is the logic we use to assign intrabar ​volume to up or down slots:  • If the intrabar's open and close values are different, their relative position is used.  • If the intrabar's open and close values are the same, the difference between the intrabar's close and the previous intrabar's close is used.  • As a last resort, when there is no movement during an intrabar and it closes at the same price as the previous intrabar, the last known polarity is used. Once all intrabars making up a chart bar have been analyzed and the up or down property of each intrabar's ​volume determined, the up volumes are added and the down volumes subtracted. The resulting value is ​volume delta for that chart bar. █   FEATURES CVD Candles Cumulative ​Volume Delta Candles present ​volume delta information as it evolves during a period of time. This is how each candle's levels are calculated:  • open : Each candle's' open level is the cumulative ​volume delta for the current period at the start of the bar.   This value becomes zero on the first candle following a ​CVD reset.   The candles after the first one always open where the previous candle closed.   The candle's high, low and close levels are then calculated by adding or subtracting a ​volume value to the open.  • high : The highest ​​volume delta value found in intrabars. If it is not higher than the ​volume delta for the bar, then that candle will have no upper wick.  • low : The lowest ​​volume delta value found in intrabars. If it is not lower than the ​volume delta for the bar, then that candle will have no lower wick.  • close : The aggregated ​volume delta for all intrabars. If ​volume delta is positive for the chart bar, then the candle's close will be higher than its open, and vice versa. The candles are plotted in one of two configurable colors, depending on the polarity of ​volume delta for the bar. CVD resets The "cumulative" part of the indicator's name stems from the fact that calculations accumulate during a period of time. This allows you to analyze the progression of ​volume delta across manageable chunks, which is often more useful than looking at ​volume delta cumulated from the beginning of a chart's history. You can configure the reset period using the "CVD Resets" input, which offers the following selections:  • None : Calculations do not reset.  • On a fixed higher timeframe : Calculations reset on the higher timeframe you select in the "Fixed higher timeframe" field.  • At a fixed time that you specify.  • At the beginning of the regular session .  • On a stepped higher timeframe : Calculations reset on a higher timeframe automatically stepped using the chart's timeframe and following these rules: Chart TF ​HTF < 1min 1H < 3H 1D <= 12H 1W < 1W 1M >= 1W 1Y The indicator's background shows where resets occur. Intrabar precision The precision of calculations increases with the number of intrabars analyzed for each chart bar. It is controlled through the script's "Intrabar precision" input, which offers the following selections:  • Least precise, covering many chart bars  • Less precise, covering some chart bars  • More precise, covering less chart bars  • Most precise, 1min intrabars As there is a limit to the number of intrabars that can be analyzed by a script, a tradeoff occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. Total ​volume candles You can choose to display candles showing the total intrabar ​volume for the chart bar. This provides you with more context to evaluate a bar's ​volume delta by showing it relative to the sum of intrabar ​volume. Note that because of the reasons explained in the "NOTES" section further down, the total ​volume is the sum of all intrabar ​​volume rather than the ​volume of the bar at the chart's timeframe. Total ​volume candles can be configured with their own up and down colors. You can also control the opacity of their bodies to make them more or less prominent. This publication's chart shows the indicator with total ​volume candles. They are turned off by default, so you will need to choose to display them in the script's inputs for them to plot. Divergences Divergences occur when the polarity of ​volume delta does not match that of the chart bar. You can identify divergences by coloring the ​CVD candles differently for them, or by coloring the indicator's background. Information box An information box in the lower-left corner of the indicator displays the HTF used for resets, the ​LTF used for intrabars, and the average quantity of intrabars per chart bar. You can hide the box using the script's inputs. █   INTERPRETATION The first thing to look at when analyzing ​CVD candles is the side of the zero line they are on, as this tells you if ​CVD is generally ​bullish or ​bearish. Next, one should consider the relative position of successive candles, just as you would with a price chart. Are successive candles trending up, down, or stagnating? Keep in mind that whatever trend you identify must be considered in the context of where it appears with regards to the zero line; an uptrend in a negative ​CVD (below the zero line) may not be as powerful as one taking place in positive ​CVD values, but it may also predate a movement into positive ​CVD territory. The same goes with stagnation; a trader in a long position will find stagnation in positive ​CVD territory less worrisome than stagnation under the zero line. After consideration of the bigger picture, one can drill down into the details. Exactly what you are looking for in markets will, of course, depend on your trading methodology, but you may find it useful to:   • Evaluate ​volume delta for the bar in relation to price movement for that bar.   • Evaluate the proportion that ​​volume delta represents of total ​volume.   • Notice divergences and if the chart's candle shape confirms a hesitation point, as a Doji would.   • Evaluate if the progress of ​CVD candles correlates with that of chart bars.   • Analyze the wicks. As with price candles, long wicks tend to indicate weakness. Always keep in mind that unless you have chosen not to reset it, your ​CVD resets for each period, whether it is fixed or automatically stepped. Consequently, any trend from the preceding period must re-establish itself in the next. █   NOTES Know your volume Traders using ​volume information should understand the ​volume data they are using: where it originates and what transactions it includes, as this can vary with instruments, sectors, exchanges, timeframes, and between historical and realtime bars. The information used to build a chart's bars and display ​volume comes from data providers (exchanges, brokers, etc.) who often maintain distinct feeds for intraday and ​end-of-day (​EOD) timeframes. How ​volume data is assembled for the two feeds depends on how instruments are traded in that sector and/or the ​volume reporting policy for each feed. Instruments from crypto and forex markets, for example, will often display similar ​volume on both feeds. Stocks will often display variations because block trades or other types of trades may not be included in their intraday ​volume data. ​Futures will also typically display variations. Note that as intraday vs ​EOD variations exist for historical bars on some instruments, differences may also exist between the realtime feeds used on intraday vs 1D or greater timeframes for those same assets. Realtime reporting rules will often be different from historical feed reporting rules, so variations between realtime feeds will often be different from the variations between historical feeds for the same instrument. The Volume X-ray indicator can help you analyze differences between intraday and ​EOD ​volumes for the instruments you trade. If every unit of ​volume is both bought by a buyer and sold by a seller, how can ​volume delta make sense? Traders who do not understand the mechanics of matching engines (the exchange software that matches orders from buyers and sellers) sometimes argue that the concept of ​volume delta is flawed, as every unit of ​volume is both bought and sold. While they are rigorously correct in stating that every unit of ​volume is both bought and sold, they overlook the fact that information can be mined by analyzing variations in the price of successive ticks, or in our case, intrabars. Our calculations model the situation where, in fully automated order handling, market orders are generally matched to limit orders sitting in the order book. Buy market orders are matched to quotes at the ask level and sell market orders are matched to quotes at the bid level. As explained earlier, we use the same logic when comparing intrabar prices. While using intrabar analysis does not produce results as precise as when individual transactions — or ticks — are analyzed, results are much more precise than those of methods using only chart prices. Not only does the concept underlying ​volume delta make sense, it provides a window on an oft-overlooked variable which, with price and time, is the only basic information representing market activity. Furthermore, because the calculation of ​volume delta also uses price and time variations, one could conceivably surmise that it can provide a more complete model than ones using price and time only. Whether or not ​volume delta can be useful in your trading practice, as usual, is for you to decide, as each trader's methodology is different. For Pine Script™ coders As our latest Polarity Divergences publication, this script uses the recently released request.security_lower_tf() Pine Script™ function discussed in this blog post . It works differently from the usual request.security() in that it can only be used at LTFs, and it returns an array containing one value per intrabar. This makes it much easier for programmers to access intrabar information. Look first. Then leap.
אינדיקטור Pine Script®
מאת ‎TradingView‎
234
Trend Analysis Index [CC]The Trend Analysis Index was created by Adam White and not to be confused with the Trend Analysis Indicator that I also published. This indicator operates under the same idea but using a completely different calculation to achieve similar results. The idea behind this indicator is for a combination of volatility and trend confirmation. If the indicator is above it's signal line then the stock is very volatile and vice versa. If the stock is currently trending as in above a chosen moving average for example and the indicator falls below the signal line then there is a pretty good chance in a trend reversal. The recommended buy and sell system to use is to pair this indicator with a moving average crossover system which I have included in the script. Buy when the indicator is above it's signal and the shorter moving average crosses above the longer moving average. For selling you would do the same and sell when the indicator is above it's signal and the shorter moving average crosses below the longer moving average. I have included strong buy and sell signals in addition to the normal ones so stronger signals are darker in color and normal signals are lighter in color. Let me know what other indicators or scripts you would like to see me publish!
אינדיקטור Pine Script®
מאת ‎cheatcountry‎
[Sextan] M-Oscillator BacktestLevel: 1 NOTE: This is a request by @scantor516 to backtest M-Oscillator by Mango2Juice with my Sextan framework. I ONLY take 5 minutes to perform it and how much time would you cost for this work? Courtesy of Mango2Juice for M-Oscillator script. You can backtest many of my indicators in minutes now! Of course,you can define your own indicator in the highlighted area in compliance with the uniform format, which guarantee when you use "Indicator on Indicator" function, it would not produce any error. Background Backtesting of technical indicators and strategies is the most common way to understand a quantitative strategy. However, the complicated configuration and adaptation work of backtesting many quantitative tools makes many traders who do not understand the code daunted. Moreover, although I have written a lot of strategies, I am still not very satisfied with the backtest configuration and writing efficiency. Therefore, I have been thinking about how to build a backtesting framework that can quickly and easily evaluate the backtesting performance of any indicator with a "long/short entry" indicator, that is, a "simple backtesting tool for dummies". The performance requirements should be stable, and the operation should be simple and convenient. It is best to "copy", "paste", and "a few mouse clicks" to complete the quick backtest and evaluation of a new indicator. Luckily, I recently realized that TradingView provides an "Indicator on Indicator" feature, which is the perfect foundation for doing "hot swap" backtesting. My basic idea is to use a two-layer design. The first layer is the technical indicator signal source that needs to be embedded, which is only used to provide buy and sell signals of custom strategies; the second layer is the trading system, which is used to receive the output signals of the first layer, and filter the signals according to the agreed specifications. , Take Profit, Stop Loss, draw buy and sell signals and cost lines, define and send custom buy and sell alert messages to mobile phones, social software or trading interfaces. In general, this two-layer design is a flexible combination of "death and alive", which can meet the needs of most traders to quickly evaluate the performance of a certain technical indicator. The first layer here is flexible. Users can insert their own strategy codes according to my template, and they can draw buy and sell signals and output them to the second layer. The second layer is fixed, and the overall framework is solidified to ensure the stability and unity of the trading system. It is convenient to compare different or similar strategies under the same conditions. Finally, all trading signals are drawn on the chart, and the output strategy returns. test report. The main function: The first layer: "{Sextan} Your Indicator Source", the script provides a template for personalized strategy input, and the signal and definition interfaces ensure full compatibility with the second layer. Backtesting is performed stably in the backtesting framework of the layer. The first layer of this script is also relatively simple: enter your script in the highlighted custom script area, and after ensuring the final buy and sell signals long = bool condition, short = bool condition, the design of the first layer is considered complete. Input it into the PINE script editor of TradingView, save it and add it to the chart, you can see the pulse sequence in yellow (buy) and purple (sell) on the sub-picture, corresponding to the main picture, you can subjectively judge that the quality of the trading point of the strategy is good Bad. The second layer: "{Sextan} PINEv4 Sextans Backtest Framework". This script is the standardized trading system strategy execution and alarm, used to generate the final report of the strategy backtest and some key indicators that I have customized that I find useful, such as: winning rate , Odds, Winning Surface, Kelly Ratio, Take Profit and Stop Loss Thresholds, Trading Frequency, etc. are evaluated according to the Kelly formula. To use the second layer, first load it into the TrainingView chart, no markers will appear on the chart, since you have not specified any strategy source signals, click on the gear-shaped setting next to the "{Sextan} PINEv4 Sextans BTFW" header button, you can open the backtest settings, the first item is to select your custom strategy source. Because we have added the strategy source to the chart in the previous step, you can easily find an option "{Sextan} Your Indicator Source: Signal" at the bottom of the list, this is the strategy source input we need, select and confirm , you can see various markers on the main graph, and quickly generate a backtesting profit graph and a list of backtesting reports. You can generate files and download the backtesting reports locally. You can also click the gear on the backtest chart interface to customize some conditions of the backtest, including: initial capital amount, currency type, percentage of each order placed, amount of pyramid additions, commission fees, slippage, etc. configuration. Note: The configuration in the interface dialog overrides the same configuration implemented by the code in the backtest script. How to output charts: The first layer: "{Sextan} Your Indicator Source", the output of this script is the pulse value of yellow and purple, yellow +1 means buy, purple -1 means sell. The second layer: PINEv4 Sextans Backtest Framework". The output of this script is a bit complicated. After all, it is the entire trading system with a lot of information: 1. Blue and red arrows. The blue upward arrow indicates long position, the red downward arrow indicates short position, and the horizontal bar at the end of the purple arrow indicates take profit or stop loss exit. 2. Red and green lines. This is the holding cost line of the strategy, green represents the cost of holding a long position, and red represents the cost of holding a short position. The cost line is a continuous solid line and the price action is relatively close. 3. Green and yellow long take profit and stop loss area and green and yellow long take profit and stop loss fork. Once a long position is held, there is a conditional order for take profit and stop loss. The green horizontal line is the long take profit ratio line, and the yellow is the long stop loss ratio line; the green cross indicates the long take profit price, and the yellow cross indicates the long position. Stop loss price. It's worth noting that the prongs and wires don't necessarily go together. Because of the optimization of the algorithm, for a strong market, the take profit will occur after breaking the take profit line, and the profit will not be taken until the price falls. 4. The purple and red short take profit and stop loss area and the purple red short stop loss fork. Once a short position is held, there will be a take profit and stop loss conditional order, the red is the short take profit ratio line, and the purple is the short stop loss ratio line; the red cross indicates the short take profit price, and the purple cross indicates the short stop loss price. 5. In addition to the above signs, there are also text and numbers indicating the profit and loss values ​​of long and short positions. "L" means long; "S" means short; "XL" means close long; "XS" means close short. TradingView Strategy Tester Panel: The overview graph is an intuitive graph that plots the blue (gain) and red (loss) curves of all backtest periods together, and notes: the absolute value and percentage of net profit, the number of all closed positions, the winning percentage, the profit factor, The maximum trading loss, the absolute value and ratio of the average trading profit and loss, and the average number of K-lines held in all trades. Another is the performance summary. This is to display all long and short statistical indicators of backtesting in the form of a list, such as: net profit, gross profit, Sharpe ratio, maximum position, commission, times of profit and loss, etc. Finally, the transaction list is a table indexed by the transaction serial number, showing the signal direction, date and time, price, profit and loss, accumulated profit and loss, maximum transaction profit, transaction loss and other values. Remarks Finally, I will explain that this is just the beginning of this model. I will continue to optimize the trading system of the second layer. Various optimization feedback and suggestions are welcome. For valuable feedback, I am willing to provide some L4/L5 technical indicators as rewards for free subscription rights.
אינדיקטור Pine Script®
מאת ‎blackcat1402‎
Weis pip zigzag jayyWhat you see here is the Weis pip zigzag wave plotted directly on the price chart.  This script is the companion to the Weis pip wave (  ) which is plotted in the lower panel of the displayed chart and can be used as an alternate way of plotting the same results.  The Weis pip zigzag wave shows how far in terms of price a Weis wave has traveled through the duration of a Weis wave.  The Weis pip zigzag wave is used in combination with the Weis cumulative volume wave.  The two waves must be set to the same "wave size". To use this script you must set the wave size.  Using the traditional Weis method simply enter the desired wave size in the box "Select Weis Wave Size"  In this example, it is set to 5.  Each wave for each security and each timeframe requires its own wave size.  Although not the traditional method a more automatic way to set wave size would be to use ATR.  This is not the true Weis method but it does give you similar waves and, importantly, without the hassle described above. Once the Weis wave size is set then the pip wave will be shown. I have put a pip zigzag of a 5 point Weis wave on the bar chart - that is a different script.  I have added it to allow your eye to see what a Weis wave looks like.  You will notice that the wave is not in straight lines connecting wave tops to bottoms this is a function of the limitations of Pinescript version 1.  This script would need to be in version 4 to allow straight lines.  There are too many calculations within this script to allow conversion to Pinescript version 4 or even Version 3.  I am in the process of rewriting this script to reduce the number of calculations and streamline the algorithm.    The numbers plotted on the chart are calculated to be relative numbers.  The script is limited to showing only three numbers vertically.  Only the highest three values of a number are shown.  For example, if the highest recent pip value is 12,345 only the first 3 numerals would be displayed ie 123.  But suppose there is a recent value of 691.  It would not be helpful to display 691 if the other wave size is shown as 123. To give the appropriate relative value the script will show a value of 7 instead of 691. This informs you of the relative magnitude of the values.  This is done automatically within the script.  There is likely no need to manually override the automatically calculated value.  I will create a video that demonstrates the manual override method. What is a Weis wave?  David Weis has been recognized as a Wyckoff method analyst he has written two books one of which, Trades About to Happen, describes the evolution of the now popular Weis wave.  The method employed by Weis is to identify waves of price action and to compare the strength of the waves on characteristics of wave strength.  Chief among the characteristics of strength is the cumulative volume of the wave.  There are other markers that Weis uses as well for example how the actual price difference between the start of the Weis wave from start to finish.  Weis also uses time, particularly when using a Renko chart.  Weis specifically uses candle or bar closes to define all wave action ie a line chart.   David Weis did a futures  io video which is a popular source of information about his method. This is the identical script with the identical settings but without the offending links. If you want to see the pip Weis method in practice then search Weis pip wave.  If you want to see Weis chart in pdf then message me and I will give a link or the Weis pdf.  Why would you want to see the Weis chart for May 27, 2020?  Merely to confirm the veracity of my algorithm.  You could compare my Weis chart here () from the same period to the David Weis chart from May 27. Both waves are for the ES!1 4 hour chart and both for a wave size of 5. 
אינדיקטור Pine Script®
מאת ‎jayy‎
22
TA Basics: further "Steps" with our Moving AverageSo far in this series of posts, we have worked thru creating a basic zero-lag moving average, then moved forward all the way to coding a "Fibonacci" Weighted Moving Average. in this post we take a look at a technique that can help traders minimize noise in the underlying data and get better insight on the changes that are happening in the data series represented by the moving average. we'll look at adding "stepping" to our Fibonacci Moving Average as an example. we introduce the Stepping Fibonacci Moving Average , or Step_FiMA note that you can use the same technique with any plot you may have. feel free to copy or leverage the relevant parts of the script - the script is commented to make this easier. How is this useful? ================== with "stepping", you get your indicator to "round" the outcome into pre-specified bands or ranges. this works very similar to how, for example, range or Renko charts work. you can easily see the difference in the chart above once we look at a non-stepped and a stepping moving average of the same length side-by-side the more granular your timeframe is, you will see the effect of the stepping clearer - here's how the same chart looks when we go into the 1-hr aggregation Notes about this script ==================== there are couple of pieces i wanted to highlight in the script if you plan to use some of it : 1 - the step(x) function is meant to try to automatically pick the best "suitable" step size based on the range of the underlying series (for example, the closing price). these ranges i included here in the code are just my own "best choices" - you are totally welcome to adjust these ranges and the resulting step size to your own preference 2 - we applied the stepping as a user-choice. user can choose a manual entry, or "0" to get the code to automatically pick the step size, or enter -1 (or actually any value below zero) to cancel the stepping option altogether - this gives us some flexibility on how to use the stepping in an indicator 3 - very important (and somehow confusing): on the "rounding" approach: the magic math formula that actually creates the stepping is this one result = round(input / step) * step now, this tells the script to "round" the result up or down (the basic rounding) -- so for example, a price of 17 with a step of 5 would be rounded (down) to 15, where as a price of 18 would be rounded "up" to 20 -- this is not the way some of us would expect or want, cause the price never reached 20 and they would want an 18 to still be rounded to 15 - and the stepping line not to show 20 *until* the price actually hits or exceeds 20 -- in that case, you would need to replace the function "round" with the function "floor" -- so the new formula becomes: floor(input / step) * step -- in an ideal world, we can make this rounding choice a user-option in the settings -- maybe in an improved version 4 - we kept the smoothing option, and it takes place before the stepping is applied - we continue to use that smoothing to further minimize the level changes in the FiMA line. I hope you find this script useful in your journey with technical analysis and DIY scripting, and good luck in your trading.
אינדיקטור Pine Script®
מאת ‎RedKTrader‎
Plotchar - How to draw external symbols on a chartHey everyone It's been a while :) but still on holidays and working on the website. I'll resume the scripts sharing shortly once I'll get back home For today, I wanted to share a very useful script that is going to make you a top of money 100% guaranteed and you'll even have a Lamborghini delivered at your place by tomorrow... (imagine some followers would believe me for this) This "script" is a proof of concept that you can draw external Unicode symbols on a chart. If you're tired with the plotshape shapes by default, you can use some others - I usually find mine there emojipedia.org What are the use cases? - Draw a dead skeleton when your stop-loss is hit - Draw a winning cup when your take profit is hit - Draw a coffin when you run out of capital FAQ Q: Does this script has any interest? A: I'm not sure myself Q: Will you make money using it? A: I'm not a financial advisor but ... very likely NO Q: Is it cool though? A: Hell yeah!! Be sure to hit the thumbs up so that I'll share real scripts the next times and not "joke scripts". I promise it's the first and last time I'm sharing such a script Dave ____________________________________________________________ - I'm an officially approved PineEditor/LUA/MT4 approved mentor on codementor. You can request a coaching with me if you want and I'll teach you how to build kick-ass indicators and strategies Jump on a 1 to 1 coaching with me - You can also hire for a custom dev of your indicator/strategy/bot/chrome extension/python
אינדיקטור Pine Script®
מאת ‎Daveatt‎
3
How to avoid repainting when using security() - PineCoders FAQNOTE The non-repainting technique in this publication that relies on bar states is now deprecated, as we have identified inconsistencies that undermine its credibility as a universal solution. The outputs that use the technique are still available for reference in this publication. However, we do not endorse its usage. See this publication for more information about the current best practices for requesting HTF data and why they work. This indicator shows how to avoid repainting when using the security() function to retrieve information from higher timeframes. What do we mean by repainting? Repainting is used to describe three different things, in what we’ve seen in TV members comments on indicators: 1. An indicator showing results that change during the realtime bar, whether the script is using the security() function or not, e.g., a Buy signal that goes on and then off, or a plot that changes values. 2. An indicator that uses future data not yet available on historical bars. 3. An indicator that uses a negative offset= parameter when plotting in order to plot information on past bars. The repainting types we will be discussing here are the first two types, as the third one is intentional—sometimes even intentionally misleading when unscrupulous script writers want their strategy to look better than it is. Let’s be clear about one thing: repainting is not caused by a bug ; it is caused by the different context between historical bars and the realtime bar, and script coders or users not taking the necessary precautions to prevent it. Why should repainting be avoided? Repainting matters because it affects the behavior of Pine scripts in the realtime bar, where the action happens and counts, because that is when traders (or our systems) take decisions where odds must be in our favor. Repainting also matters because if you test a strategy on historical bars using only OHLC values, and then run that same code on the realtime bar with more than OHLC information, scripts not properly written or misconfigured alerts will alter the strategy’s behavior. At that point, you will not be running the same strategy you tested, and this invalidates your test results , which were run while not having the additional price information that is available in the realtime bar. The realtime bar on your charts is only one bar, but it is a very important bar. Coding proper strategies and indicators on TV requires that you understand the variations in script behavior and how information available to the script varies between when the script is running on historical and realtime bars. How does repainting occur? Repainting happens because of something all traders instinctively crave: more information. Contrary to trader lure, more information is not always better. In the realtime bar, all TV indicators (a.k.a. studies ) execute every time price changes (i.e. every tick ). TV strategies will also behave the same way if they use the calc_on_every_tick = true parameter in their strategy() declaration statement (the parameter’s default value is false ). Pine coders must decide if they want their code to use the realtime price information as it comes in, or wait for the realtime bar to close before using the same OHLC values for that bar that would be used on historical bars. Strategy modelers often assume that using realtime price information as it comes in the realtime bar will always improve their results. This is incorrect. More information does not necessarily improve performance because it almost always entails more noise. The extra information may or may not improve results; one cannot know until the code is run in realtime for enough time to provide data that can be analyzed and from which somewhat reliable conclusions can be derived. In any case, as was stated before, it is critical to understand that if your strategy is taking decisions on realtime tick data, you are NOT running the same strategy you tested on historical bars with OHLC values only. How do we avoid repainting? It comes down to using reliable information and properly configuring alerts, if you use them. Here are the main considerations: 1. If your code is using security() calls, use the syntax we propose to obtain reliable data from higher timeframes. 2. If your script is a strategy, do not use the calc_on_every_tick = true parameter unless your strategy uses previous bar information to calculate. 3. If your script is a study and is using current timeframe information that is compared to values obtained from a higher timeframe, even if you can rely on reliable higher timeframe information because you are correctly using the security() function, you still need to ensure the realtime bar’s information you use (a cross of current close over a higher timeframe MA, for example) is consistent with your backtest methodology, i.e. that your script calculates on the close of the realtime bar. If your system is using alerts, the simplest solution is to configure alerts to trigger Once Per Bar Close . If you are not using alerts, the best solution is to use information from the preceding bar. When using previous bar information, alerts can be configured to trigger Once Per Bar safely. What does this indicator do? It shows results for 9 different ways of using the security() function and illustrates the simplest and most effective way to avoid repainting, i.e. using security() as in the example above. To show the indicator’s lines the most clearly, price on the chart is shown with a black line rather than candlesticks. This indicator also shows how misusing security() produces repainting. All combinations of using a 0 or 1 offset to reference the series used in the security() , as well as all combinations of values for the gaps= and lookahead= parameters are shown. The close in the call labeled “BEST” means that once security has reached the upper timeframe (1 day in our case), it will fetch the previous day’s value. The gaps= parameter is not specified as it is off by default and that is what we need. This ensures that the value returned by security() will not contain na values on any of our chart’s bars. The lookahead security() to use the last available value for the higher timeframe bar we are using (the previous day, in our case). This ensures that security() will return the value at the end of the higher timeframe, even if it has not occurred yet. In our case, this has no negative impact since we are requesting the previous day’s value, with has already closed. The indicator’s Settings/Inputs allow you to set: - The higher timeframe security() calls will use - The source security() calls will use - If you want identifying labels printed on the lines that have no gaps (the lines containing gaps are plotted using very thick lines that appear as horizontal blocks of one bar in length) For the lines to be plotted, you need to be on a smaller timeframe than the one used for the security() calls. Comments in the code explain what’s going on. Look first. Then leap.
אינדיקטור Pine Script®
מאת ‎PineCoders‎
173
Dragon-Bot - Default ScriptDragon-Script is a framework to make it as easy as possible to test your own strategies and set alerts for external execution bots. This is the alerts version of the script. The script has many features build in, like: 1) A ping/pong mechanism between longs and shorts 2) A stop-loss 3) Trailing Stops with several ways to calculate them. 4) 2 different ways to flip from long to short. The script is divided into several parts. The first part of the script is used to set all the variables. You should normally never change the first part except for the comments at the top. The second part of the script is the part where you initialise all your indicators. Several indicators can be found on Tradingview and on other sites. Please keep in mind that all the variable names used in the indicator should be unique. (all the … = … parts) The third part of the script, is the most important part of the script. Here you can create the entry and exit points. Let’s look at the OPENLONG function to explain this part: The first variables are all the possible entries; These are longentry1 till longentry5. You can add many more if you like. The variables are all initialised as being false. This way the script can set a value to true if an entry happens. The if function is the actual logic: You could say “if this is true” then (the line below the if function) longentry1 := (becomes) true. In this case we have said: “if this is true” then (the line below the if function) longentry1 := (becomes) true when the current close is larger than the close that is 1 back. The last part is the makelong_funct. This part says that if any of the entries are true, the whole function is true. The last part of the script is the actual execution. Here the alerts are plotted and the back test strategies are opened and closed. We hope you guys like it and all feedback is welcome!
אינדיקטור Pine Script®
מאת ‎Dragon-Bot‎
1
BTC - Cycle Integrity Index (CII) BTC - Cycle Integrity Index (CII) | RM Are we following a calendar or a capital flow? Is the Halving still the heartbeat of Bitcoin, or has the institutional "Engine" taken over? The most polarized debate in the digital asset space today centers on a single question: Is the 4-year Halving Cycle dead? While some market participants wait for a pre-ordained calendar countdown, the reality of 2026 suggests that visual guesswork is no longer sufficient. As institutional gravity takes hold, we cannot rely on the simple "Clock" of the past. Instead, we must audit the Integrity of the present. The Cycle Integrity Index (CII) was engineered to move beyond simple price action and provide a clinical answer to the market's biggest mystery: "Is this trend supported by structural substance, or is it merely speculative foam?" By aggregating eight diverse Pillars into a single 0-100% score, this model uses Gaussian Distributions and Sigmoid Normalization to distinguish between professional accumulation and retail-driven chaos. We aren't guessing where we are in a cycle; we are measuring the internal health of the asset's engine in real-time. Why these 8 Pillars? The CII does not rely on a single indicator because the "New Era" of Bitcoin is multi-dimensional. To capture the full picture, I selected eight specific pillars that cover the three layers of market truth: • The Capital Layer: Global Liquidity (M2) and ETF Flows (Wall Street Absorption). • The Network Layer: Mining Difficulty and Security Backbone expansion. • The Sentiment Layer: Long-Term Holder conviction, Valuation Heat (MVRV), and Corporate Adoption (MSTR). While alternatives like the Pi Cycle or RSI exist, they are often "one-dimensional." The CII is a synthesis—a modular engine where every part validates the others. How the Calculation Works The CII is a sophisticated model for Bitcoin. It aggregates 8 diverse pillars into a single 0-100% score in the following way: • Mathematical Normalization: We don't just use raw prices. We use Gaussian Distributions to find "Institutional DNA" in drawdowns and Sigmoid (S-Curve) functions to score volatility and valuation. • Dynamic Weighting: The index is modular. If a data source (like a specific on-chain metric) is toggled off, the engine automatically redistributes the weight among the active sensors so the final integrity score is always balanced to 100%. • Multi-Source Integration: The script pulls from Global Liquidity (M2), ETF flows, Corporate Treasury premiums (MSTR), and Network Difficulty to create a truly "Full-Stack" view of the asset. The 8 Pillars of Integrity Pillar 1: Drawdown DNA The "Identity Crisis" Filter • Concept: Audits the depth of corrections to distinguish between "Institutional Floors" and "Retail Panics." • Logic: Historically, retail crashes reached -80%, while institutions view -20% to -25% as primary value entries. • Implementation: Uses a Gaussian (Normal) Distribution centered at -25%. Scores of 10/10 are awarded for holding institutional targets; scores decay as drawdowns accelerate toward legacy "crash" levels. Basis: DNA Drawdown Pillar 2: Volatility Regime The "Smoothness" Audit • Concept: Measures the "vibration" of the trend. High-integrity moves are characterized by "smooth" price action. • Logic: Erratic volatility signals speculative bubbles; consistent "volatility clusters" indicate professional trend-following. • Implementation: Calculates a Z-Score of the 14-day ATR against a 100-day benchmark. This is passed through a Sigmoid function to penalize "chaotic" price shocks while rewarding stability. Basis: RVPM Pillar 3: Liquidity Sync (Global M2) The Macro Heartbeat • Concept: Audits whether price growth is fueled by monetary expansion or internal speculative leverage. • Logic: True cycle integrity requires a positive correlation between Central Bank balance sheets and price action. • Implementation: Aggregates a custom Global Liquidity Proxy (Fed, RRP, TGA, PBoC, ECB, BoJ). It measures the Pearson Correlation between BTC and M2 with a standardized 80-day transmission lag. Basis: Liquisync Pillar 4: ETF Absorption (Wall Street Entry) The "Cost Basis" Defense • Concept: Tracks the aggregate institutional cost-basis since the January 2024 Spot ETF launch. • Logic: Integrity is high when the "Wall Street Floor" is defended; it fails when the aggregate position is underwater. • Implementation: A Cumulative VWAP engine tracking the "Big 3" (IBIT, FBTC, BITB). Scoring decays based on the percentage distance the price drifts below this institutional average entry. Basis: Institutional Cost Corridor Note: Turning this to OFF will significantly expand the timeframe of the indicator on the chart (otherwise it will just start in 2024) Pillar 5: LTH Dormancy (Conviction) The HODL Floor Audit • Concept: Monitors the conviction of Long-Term Holders (LTH) to identify supply-side constraints. • Logic: Sustainable cycles require stable or increasing 1Y+ dormant supply; rapid "thawing" signals distribution. • Implementation: Uses Min-Max Normalization on the Active 1Y Supply over a 252-day window. A score of 10/10 indicates peak annual holding conviction. Basis: RHODL Proxy & VDD Multiple Pillar 6: Valuation Intensity The MVRV Heat Map • Concept: Measures market "overheat" by comparing Market Value to Realized Value. • Logic: High integrity trends rise steadily; vertical spikes in MVRV indicate "speculative foam" and bubble risk. • Implementation: Performs a Relative Rank Analysis of the MVRV Ratio over a 730-day window, passed through a high-steepness Sigmoid curve to identify extreme valuation anomalies. Pillar 7: Miner Stress The Security Backbone • Concept: Tracks Mining Difficulty to ensure network infrastructure is expanding alongside price. • Logic: Difficulty expansion signals health; drops in difficulty (Miner Stress) signal capitulation and sell-side pressure. • Implementation: Monitors the 30-day Rate of Change (ROC) of Global Mining Difficulty. Maintains a 10/10 score during expansion; decays rapidly during network contraction. Pillar 8: Corporate Adoption The MSTR NAV Proxy • Concept: Audits the MicroStrategy (MSTR) premium as a barometer for institutional demand. • Logic: A high premium indicates a willingness to pay a "convenience fee" for BTC exposure; a collapsing premium signals waning appetite. • Implementation: Calculates the Adjusted Enterprise Value (Market Cap + Debt - Cash) relative to the Net Asset Value (NAV) of its BTC holdings. Note1: Debt and share parameters are user-adjustable to maintain accuracy as corporate balance sheets evolve. Note2: I just included this because I was curious about the mNAV calculation I saw in other scripts, where the printed value often does not match exactly the propagated value from the MSTR page itself. Hence, for my live calculation, we calculate the Adjusted Enterprise Value to find the "Market NAV" (mNAV). Unlike simpler scripts that only look at Market Cap vs. Bitcoin holdings, our engine accounts for the Capital Structure . We explicitly factor in the corporate debt (approx. $8.24B long-term + $7.95B convertible notes) and subtract the cash reserves (approx. $2.18B) to find the true cost Wall Street is paying for the underlying Bitcoin. Since this will ran "old" very quickly, I recommend to update in the code by yourself from time to time, or just de-select this parameter. Interpretation Guide • Score 100% (The Perfect Storm): This represents a state of "Maximum Integrity." All 8 pillars are in perfect institutional alignment—liquidity is surging, conviction is at yearly highs, and price action is perfectly smooth. This is the hallmark of a healthy, structural parabolic run. • 75% - 100% (High Integrity): Robust trend. Price is supported by structural demand and macro tailwinds. • 35% - 75% (Equilibrium): Transition zone. The market is digesting gains or waiting for a new liquidity pulse. • 0% - 35% (Fragile): Speculative foam. Structural support has failed. • Score 0% (The Ghost Trend): Absolute structural failure. All pillars (liquidity, miners, LTH, ETFs) have broken down. Note: Due to the robust nature of the Bitcoin network, the index naturally floors around 20-30% during deep bear markets, as specific pillars (like Miner Security) rarely drop to zero. To provide a complete experience, I have included the Cycle Triad —a visualization layer consisting of the Halving, Ideal Peak, and Ideal Low. It is important to understand the role of this feature: • Benchmark Only (Not Calculated): The Triad is based purely on historical evidence from previous Bitcoin epochs. While the Halving is fixed anyway, the "Ideal Peak" or "Ideal Low" are not calculated or computed by the 8 pillars. These are user-adjustable temporal anchors drawn on the chart to provide a static map of the "Legacy 4-Year Cycle." • The Temporal Audit: The power of the CII lies in comparing the Engine (the 8 Pillars) against the Clock (the Triad) . By overlaying historical time-windows on top of our integrity math, we can see if the "New Era" is currently ahead of, behind, or perfectly in sync with the past. • The "Peak Divergence" Logic: Based on the specific models selected for this ECU—specifically Volatility Decay and Valuation Heat —traders will notice that a cycle peak often coincides with a low integrity score (Red Zone) . While the index measures structural health, a low score is a byproduct of a market that has become "too hot to handle." • Regime Detection: Although the primary goal is to audit the "New Era," the CII is highly effective at detecting overheated regimes. When the score drops toward the 25–35% range, the structural floor is giving way to speculative foam—making it a dual-purpose tool for both cycle analysis and risk management. Dashboard Calibration & Settings Cycle Triad Calibration • Ideal Peak/Trough Window: Defines the historical "Average Days" from a Halving to the cycle top and bottom. This sets the vertical anchors for the Halving, Peak, and Low labels. • Show Cycle Triad: A master toggle to enable or disable the temporal lines and labels on your dashboard. The CII Master ECU is fully modular. You can toggle individual pillars ON/OFF to focus on specific market dimensions, and calibrate the sensitivity of each sensor to match your strategic bias. • P1: Drawdown DNA Lookback (Weeks): Defines the window for the "Rolling High." Inst. Target (%): The specific percentage drawdown you define as "Institutional Support" (e.g., -25%). • P2: Volatility Regime Benchmark (Days): The historical window used to define "Normal" vs. "Abnormal" volatility. • P3: Liquidity Sync Corr. Window (Bars): The lookback for the Pearson Correlation calculation. Transmission Lag (Bars): The delay (standard 80 days) for Central Bank M2 to hit price. • P4: ETF Absorption FBTC Ticker: The data source for the ETF volume audit (Default: CBOE:FBTC). • P5: LTH Dormancy LTH Source: The ticker for 1Y+ Active Supply (Default: GLASSNODE:BTC_ACTIVE1Y). Norm. Window: The lookback (252 days) used to rank current conviction. • P6: Valuation Intensity MVRV Source: The ticker for the MVRV Ratio (Default: INTOTHEBLOCK:BTC_MVRV). Relative Window: The lookback (730 days) to calculate the valuation rank. • P7: Miner Stress Mining Diff: The data source for Global Mining Difficulty (Default: QUANDL:BCHAIN/DIFF). • P8: Corporate Adoption Shares (M) & BTC (K): The balance sheet parameters for MicroStrategy (MSTR). Update these as the company executes new purchases to maintain mNAV accuracy. Operational Usage This index is best used on the Daily (D) (recommended - description for inputs optimized for this time-window) or Weekly (W) timeframes. While the code is optimized to fetch daily data regardless of your chart setting, the structural "Integrity" of a cycle is a macro phenomenon and should be viewed with a medium-to-long-term lens. The Verdict: Is the 4-Year Cycle Still Alive? Based on the data provided by the CII Master ECU, the answer remains a nuanced "Work in Progress." The evidence presents a fascinating conflict between legacy patterns and the new institutional regime: • The Case for the Cycle: Historically, a local "Peak" in price corresponds with a "Local Low" in our integrity indicator (Red Zone). We observed this exact phenomenon in October 2025. When viewed through the lens of the "Ideal Peak" anchor, this alignment suggests that the 4-year temporal rhythm is still exerts a massive influence on market behavior. • The Case for the New Era: While the timing of the October 2025 peak followed the legacy script, the intensity did not. Previous cycle tops produced far more aggressive and persistent "Red Zone" clusters. The relative brevity of the integrity breakdown suggests that the "Institutional Era" provides a much higher floor than the retail-driven bubbles of 2017 and 2021. • The Institutional Floor: Our data shows that while "Tops" still resemble the 4-year cycle, the "Lows" now reflect a regime of constant institutional absorption. This suggests that the brutal 80% drawdowns of the past may be replaced by the "Institutional DNA" of Pillar 1. Final Outlook: As we move through 2026, the ultimate test lies in the Q3/Q4 window. While classical theory demands a "Cycle Low" during this period, the CII will be our primary auditor. We cannot definitively say the cycle is dead, but we can say it has evolved. We will not know if the 4-year low will manifest until the model either flags a total structural breakdown or confirms that the institutional "Floor" has permanently shifted the rhythm of the asset. Tags: Bitcoin, Institutional, Macro, On-chain, Liquidity, MSTR, ETF, Cycle Note to Moderators: This script is a "Master Index" that aggregates several quantitative models I have previously published on this platform (including DNA Drawdown, RVPM, and Liquisync). I am the original author of the logic and source code referenced in the "Basis" sections of the description.
אינדיקטור Pine Script®
מאת ‎Rob_Maths‎
Color█ OVERVIEW This library is a Pine Script® programming tool for advanced color processing. It provides a comprehensive set of functions for specifying and analyzing colors in various color spaces, mixing and manipulating colors, calculating custom gradients and schemes, detecting contrast, and converting colors to or from hexadecimal strings. █ CONCEPTS Color Color refers to how we interpret light of different wavelengths in the visible spectrum . The colors we see from an object represent the light wavelengths that it reflects, emits, or transmits toward our eyes. Some colors, such as blue and red, correspond directly to parts of the spectrum. Others, such as magenta, arise from a combination of wavelengths to which our minds assign a single color. The human interpretation of color lends itself to many uses in our world. In the context of financial data analysis, the effective use of color helps transform raw data into insights that users can understand at a glance. For example, colors can categorize series, signal market conditions and sessions, and emphasize patterns or relationships in data. Color models and spaces A color model is a general mathematical framework that describes colors using sets of numbers. A color space is an implementation of a specific color model that defines an exact range (gamut) of reproducible colors based on a set of primary colors , a reference white point , and sometimes additional parameters such as viewing conditions. There are numerous different color spaces — each describing the characteristics of color in unique ways. Different spaces carry different advantages, depending on the application. Below, we provide a brief overview of the concepts underlying the color spaces supported by this library. RGB RGB is one of the most well-known color models. It represents color as an additive mixture of three primary colors — red, green, and blue lights — with various intensities. Each cone cell in the human eye responds more strongly to one of the three primaries, and the average person interprets the combination of these lights as a distinct color (e.g., pure red + pure green = yellow). The sRGB color space is the most common RGB implementation. Developed by HP and Microsoft in the 1990s, sRGB provided a standardized baseline for representing color across CRT monitors of the era, which produced brightness levels that did not increase linearly with the input signal. To match displays and optimize brightness encoding for human sensitivity, sRGB applied a nonlinear transformation to linear RGB signals, often referred to as gamma correction . The result produced more visually pleasing outputs while maintaining a simple encoding. As such, sRGB quickly became a standard for digital color representation across devices and the web. To this day, it remains the default color space for most web-based content. TradingView charts and Pine Script `color.*` built-ins process color data in sRGB. The red, green, and blue channels range from 0 to 255, where 0 represents no intensity, and 255 represents maximum intensity. Each combination of red, green, and blue values represents a distinct color, resulting in a total of 16,777,216 displayable colors. CIE XYZ and xyY The XYZ color space, developed by the International Commission on Illumination (CIE) in 1931, aims to describe all color sensations that a typical human can perceive. It is a cornerstone of color science, forming the basis for many color spaces used today. XYZ, and the derived xyY space, provide a universal representation of color that is not tethered to a particular display. Many widely used color spaces, including sRGB, are defined relative to XYZ or derived from it. The CIE built the color space based on a series of experiments in which people matched colors they perceived from mixtures of lights. From these experiments, the CIE developed color-matching functions to calculate three components — X, Y, and Z — which together aim to describe a standard observer's response to visible light. X represents a weighted response to light across the color spectrum, with the highest contribution from long wavelengths (e.g., red). Y represents a weighted response to medium wavelengths (e.g., green), and it corresponds to a color's relative luminance (i.e., brightness). Z represents a weighted response to short wavelengths (e.g., blue). From the XYZ space, the CIE developed the xyY chromaticity space, which separates a color's chromaticity (hue and colorfulness) from luminance. The CIE used this space to define the CIE 1931 chromaticity diagram , which represents the full range of visible colors at a given luminance. In color science and lighting design, xyY is a common means for specifying colors and visualizing the supported ranges of other color spaces. CIELAB and Oklab The CIELAB (L*a*b*) color space, derived from XYZ by the CIE in 1976, expresses colors based on opponent process theory. The L* component represents perceived lightness, and the a* and b* components represent the balance between opposing unique colors. The a* value specifies the balance between green and red , and the b* value specifies the balance between blue and yellow . The primary intention of CIELAB was to provide a perceptually uniform color space, where fixed-size steps through the space correspond to uniform perceived changes in color. Although relatively uniform, the color space has been found to exhibit some non-uniformities, particularly in the blue part of the color spectrum. Regardless, modern applications often use CIELAB to estimate perceived color differences and calculate smooth color gradients. In 2020, a new LAB-oriented color space, Oklab , was introduced by Björn Ottosson as an attempt to rectify the non-uniformities of other perceptual color spaces. Similar to CIELAB, the L value in Oklab represents perceived lightness, and the a and b values represent the balance between opposing unique colors. Oklab has gained widespread adoption as a perceptual space for color processing, with support in the latest CSS Color specifications and many software applications. Cylindrical models A cylindrical-coordinate model transforms an underlying color model, such as RGB or LAB, into an alternative expression of color information that is often more intuitive for the average person to use and understand. Instead of a mixture of primary colors or opponent pairs, these models represent color as a hue angle on a color wheel , with additional parameters that describe other qualities such as lightness and colorfulness (a general term for concepts like chroma and saturation). In cylindrical-coordinate spaces, users can select a color and modify its lightness or other qualities without altering the hue. The three most common RGB-based models are HSL (Hue, Saturation, Lightness), HSV (Hue, Saturation, Value), and HWB (Hue, Whiteness, Blackness). All three define hue angles in the same way, but they define colorfulness and lightness differently. Although they are not perceptually uniform, HSL and HSV are commonplace in color pickers and gradients. For CIELAB and Oklab, the cylindrical-coordinate versions are CIELCh and Oklch , which express color in terms of perceived lightness, chroma, and hue. They offer perceptually uniform alternatives to RGB-based models. These spaces create unique color wheels, and they have more strict definitions of lightness and colorfulness. Oklch is particularly well-suited for generating smooth, perceptual color gradients. Alpha and transparency Many color encoding schemes include an alpha channel, representing opacity . Alpha does not help define a color in a color space; it determines how a color interacts with other colors in the display. Opaque colors appear with full intensity on the screen, whereas translucent (semi-opaque) colors blend into the background. Colors with zero opacity are invisible. In Pine Script, there are two ways to specify a color's alpha:  • Using the `transp` parameter of the built-in `color.*()` functions. The specified value represents transparency (the opposite of opacity), which the functions translate into an alpha value.  • Using eight-digit hexadecimal color codes. The last two digits in the code represent alpha directly. A process called alpha compositing simulates translucent colors in a display. It creates a single displayed color by mixing the RGB channels of two colors (foreground and background) based on alpha values, giving the illusion of a semi-opaque color placed over another color. For example, a red color with 80% transparency on a black background produces a dark shade of red. Hexadecimal color codes A hexadecimal color code (hex code) is a compact representation of an RGB color. It encodes a color's red, green, and blue values into a sequence of hexadecimal ( base-16 ) digits. The digits are numerals ranging from `0` to `9` or letters from `a` (for 10) to `f` (for 15). Each set of two digits represents an RGB channel ranging from `00` (for 0) to `ff` (for 255). Pine scripts can natively define colors using hex codes in the format `#rrggbbaa`. The first set of two digits represents red, the second represents green, and the third represents blue. The fourth set represents alpha . If unspecified, the value is `ff` (fully opaque). For example, `#ff8b00` and `#ff8b00ff` represent an opaque orange color. The code `#ff8b0033` represents the same color with 80% transparency. Gradients A color gradient maps colors to numbers over a given range. Most color gradients represent a continuous path in a specific color space, where each number corresponds to a mix between a starting color and a stopping color. In Pine, coders often use gradients to visualize value intensities in plots and heatmaps, or to add visual depth to fills. The behavior of a color gradient depends on the mixing method and the chosen color space. Gradients in sRGB usually mix along a straight line between the red, green, and blue coordinates of two colors. In cylindrical spaces such as HSL, a gradient often rotates the hue angle through the color wheel, resulting in more pronounced color transitions. Color schemes A color scheme refers to a set of colors for use in aesthetic or functional design. A color scheme usually consists of just a few distinct colors. However, depending on the purpose, a scheme can include many colors. A user might choose palettes for a color scheme arbitrarily, or generate them algorithmically. There are many techniques for calculating color schemes. A few simple, practical methods are:  • Sampling a set of distinct colors from a color gradient.  • Generating monochromatic variants of a color (i.e., tints, tones, or shades with matching hues).  • Computing color harmonies — such as complements, analogous colors, triads, and tetrads — from a base color. This library includes functions for all three of these techniques. See below for details. █ CALCULATIONS AND USE Hex string conversion The `getHexString()` function returns a string containing the eight-digit hexadecimal code corresponding to a "color" value or set of sRGB and transparency values. For example, `getHexString(255, 0, 0)` returns the string `"#ff0000ff"`, and `getHexString(color.new(color.red, 80))` returns `"#f2364533"`. The `hexStringToColor()` function returns the "color" value represented by a string containing a six- or eight-digit hex code. The `hexStringToRGB()` function returns a tuple containing the sRGB and transparency values. For example, `hexStringToColor("#f23645")` returns the same value as color.red . Programmers can use these functions to parse colors from "string" inputs, perform string-based color calculations, and inspect color data in text outputs such as Pine Logs and tables. Color space conversion All other `get*()` functions convert a "color" value or set of sRGB channels into coordinates in a specific color space, with transparency information included. For example, the tuple returned by `getHSL()` includes the color's hue, saturation, lightness, and transparency values. To convert data from a color space back to colors or sRGB and transparency values, use the corresponding `*toColor()` or `*toRGB()` functions for that space (e.g., `hslToColor()` and `hslToRGB()`). Programmers can use these conversion functions to process inputs that define colors in different ways, perform advanced color manipulation, design custom gradients, and more. The color spaces this library supports are:  • sRGB  • Linear RGB (RGB without gamma correction)  • HSL, HSV, and HWB  • CIE XYZ and xyY  • CIELAB and CIELCh  • Oklab and Oklch Contrast-based calculations Contrast refers to the difference in luminance or color that makes one color visible against another. This library features two functions for calculating luminance-based contrast and detecting themes. The `contrastRatio()` function calculates the contrast between two "color" values based on their relative luminance (the Y value from CIE XYZ) using the formula from version 2 of the Web Content Accessibility Guidelines (WCAG) . This function is useful for identifying colors that provide a sufficient brightness difference for legibility. The `isLightTheme()` function determines whether a specified background color represents a light theme based on its contrast with black and white. Programmers can use this function to define conditional logic that responds differently to light and dark themes. Color manipulation and harmonies The `negative()` function calculates the negative (i.e., inverse) of a color by reversing the color's coordinates in either the sRGB or linear RGB color space. This function is useful for calculating high-contrast colors. The `grayscale()` function calculates a grayscale form of a specified color with the same relative luminance. The functions `complement()`, `splitComplements()`, `analogousColors()`, `triadicColors()`, `tetradicColors()`, `pentadicColors()`, and `hexadicColors()` calculate color harmonies from a specified source color within a given color space (HSL, CIELCh, or Oklch). The returned harmonious colors represent specific hue rotations around a color wheel formed by the chosen space, with the same defined lightness, saturation or chroma, and transparency. Color mixing and gradient creation The `add()` function simulates combining lights of two different colors by additively mixing their linear red, green, and blue components, ignoring transparency by default. Users can calculate a transparency-weighted mixture by setting the `transpWeight` argument to `true`. The `overlay()` function estimates the color displayed on a TradingView chart when a specific foreground color is over a background color. This function aids in simulating stacked colors and analyzing the effects of transparency. The `fromGradient()` and `fromMultiStepGradient()` functions calculate colors from gradients in any of the supported color spaces, providing flexible alternatives to the RGB-based color.from_gradient() function. The `fromGradient()` function calculates a color from a single gradient. The `fromMultiStepGradient()` function calculates a color from a piecewise gradient with multiple defined steps. Gradients are useful for heatmaps and for coloring plots or drawings based on value intensities. Scheme creation Three functions in this library calculate palettes for custom color schemes. Scripts can use these functions to create responsive color schemes that adjust to calculated values and user inputs. The `gradientPalette()` function creates an array of colors by sampling a specified number of colors along a gradient from a base color to a target color, in fixed-size steps. The `monoPalette()` function creates an array containing monochromatic variants (tints, tones, or shades) of a specified base color. Whether the function mixes the color toward white (for tints), a form of gray (for tones), or black (for shades) depends on the `grayLuminance` value. If unspecified, the function automatically chooses the mix behavior with the highest contrast. The `harmonyPalette()` function creates a matrix of colors. The first column contains the base color and specified harmonies, e.g., triadic colors. The columns that follow contain tints, tones, or shades of the harmonic colors for additional color choices, similar to `monoPalette()`. █ EXAMPLE CODE The example code at the end of the script generates and visualizes color schemes by processing user inputs. The code builds the scheme's palette based on the "Base color" input and the additional inputs in the "Settings/Inputs" tab:  • "Palette type" specifies whether the palette uses a custom gradient, monochromatic base color variants, or color harmonies with monochromatic variants.  • "Target color" sets the top color for the "Gradient" palette type.  • The "Gray luminance" inputs determine variation behavior for "Monochromatic" and "Harmony" palette types. If "Auto" is selected, the palette mixes the base color toward white or black based on its brightness. Otherwise, it mixes the color toward the grayscale color with the specified relative luminance (from 0 to 1).  • "Harmony type" specifies the color harmony used in the palette. Each row in the palette corresponds to one of the harmonious colors, starting with the base color. The code creates a table on the first bar to display the collection of calculated colors. Each cell in the table shows the color's `getHexString()` value in a tooltip for simple inspection. Look first. Then leap. █ EXPORTED FUNCTIONS Below is a complete list of the functions and overloads exported by this library. getRGB(source)   Retrieves the sRGB red, green, blue, and transparency components of a "color" value. getHexString(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channel values to a string representing the corresponding color's hexadecimal form. getHexString(source)   (Overload 2 of 2) Converts a "color" value to a string representing the sRGB color's hexadecimal form. hexStringToRGB(source)   Converts a string representing an sRGB color's hexadecimal form to a set of decimal channel values. hexStringToColor(source)   Converts a string representing an sRGB color's hexadecimal form to a "color" value. getLRGB(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channel values to a set of linear RGB values with specified transparency information. getLRGB(source)   (Overload 2 of 2) Retrieves linear RGB channel values and transparency information from a "color" value. lrgbToRGB(lr, lg, lb, t)   Converts a set of linear RGB channel values to a set of sRGB values with specified transparency information. lrgbToColor(lr, lg, lb, t)   Converts a set of linear RGB channel values and transparency information to a "color" value. getHSL(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of HSL values with specified transparency information. getHSL(source)   (Overload 2 of 2) Retrieves HSL channel values and transparency information from a "color" value. hslToRGB(h, s, l, t)   Converts a set of HSL channel values to a set of sRGB values with specified transparency information. hslToColor(h, s, l, t)   Converts a set of HSL channel values and transparency information to a "color" value. getHSV(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of HSV values with specified transparency information. getHSV(source)   (Overload 2 of 2) Retrieves HSV channel values and transparency information from a "color" value. hsvToRGB(h, s, v, t)   Converts a set of HSV channel values to a set of sRGB values with specified transparency information. hsvToColor(h, s, v, t)   Converts a set of HSV channel values and transparency information to a "color" value. getHWB(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of HWB values with specified transparency information. getHWB(source)   (Overload 2 of 2) Retrieves HWB channel values and transparency information from a "color" value. hwbToRGB(h, w, b, t)   Converts a set of HWB channel values to a set of sRGB values with specified transparency information. hwbToColor(h, w, b, t)   Converts a set of HWB channel values and transparency information to a "color" value. getXYZ(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of XYZ values with specified transparency information. getXYZ(source)   (Overload 2 of 2) Retrieves XYZ channel values and transparency information from a "color" value. xyzToRGB(x, y, z, t)   Converts a set of XYZ channel values to a set of sRGB values with specified transparency information xyzToColor(x, y, z, t)   Converts a set of XYZ channel values and transparency information to a "color" value. getXYY(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of xyY values with specified transparency information. getXYY(source)   (Overload 2 of 2) Retrieves xyY channel values and transparency information from a "color" value. xyyToRGB(xc, yc, y, t)   Converts a set of xyY channel values to a set of sRGB values with specified transparency information. xyyToColor(xc, yc, y, t)   Converts a set of xyY channel values and transparency information to a "color" value. getLAB(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of CIELAB values with specified transparency information. getLAB(source)   (Overload 2 of 2) Retrieves CIELAB channel values and transparency information from a "color" value. labToRGB(l, a, b, t)   Converts a set of CIELAB channel values to a set of sRGB values with specified transparency information. labToColor(l, a, b, t)   Converts a set of CIELAB channel values and transparency information to a "color" value. getOKLAB(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of Oklab values with specified transparency information. getOKLAB(source)   (Overload 2 of 2) Retrieves Oklab channel values and transparency information from a "color" value. oklabToRGB(l, a, b, t)   Converts a set of Oklab channel values to a set of sRGB values with specified transparency information. oklabToColor(l, a, b, t)   Converts a set of Oklab channel values and transparency information to a "color" value. getLCH(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of CIELCh values with specified transparency information. getLCH(source)   (Overload 2 of 2) Retrieves CIELCh channel values and transparency information from a "color" value. lchToRGB(l, c, h, t)   Converts a set of CIELCh channel values to a set of sRGB values with specified transparency information. lchToColor(l, c, h, t)   Converts a set of CIELCh channel values and transparency information to a "color" value. getOKLCH(r, g, b, t)   (Overload 1 of 2) Converts a set of sRGB channels to a set of Oklch values with specified transparency information. getOKLCH(source)   (Overload 2 of 2) Retrieves Oklch channel values and transparency information from a "color" value. oklchToRGB(l, c, h, t)   Converts a set of Oklch channel values to a set of sRGB values with specified transparency information. oklchToColor(l, c, h, t)   Converts a set of Oklch channel values and transparency information to a "color" value. contrastRatio(value1, value2)   Calculates the contrast ratio between two colors values based on the formula from version 2 of the Web Content Accessibility Guidelines (WCAG). isLightTheme(source)   Detects whether a background color represents a light theme or dark theme, based on the amount of contrast between the color and the white and black points. grayscale(source)   Calculates the grayscale version of a color with the same relative luminance (i.e., brightness). negative(source, colorSpace)   Calculates the negative (i.e., inverted) form of a specified color. complement(source, colorSpace)   Calculates the complementary color for a `source` color using a cylindrical color space. analogousColors(source, colorSpace)   Calculates the analogous colors for a `source` color using a cylindrical color space. splitComplements(source, colorSpace)   Calculates the split-complementary colors for a `source` color using a cylindrical color space. triadicColors(source, colorSpace)   Calculates the two triadic colors for a `source` color using a cylindrical color space. tetradicColors(source, colorSpace, square)   Calculates the three square or rectangular tetradic colors for a `source` color using a cylindrical color space. pentadicColors(source, colorSpace)   Calculates the four pentadic colors for a `source` color using a cylindrical color space. hexadicColors(source, colorSpace)   Calculates the five hexadic colors for a `source` color using a cylindrical color space. add(value1, value2, transpWeight)   Additively mixes two "color" values, with optional transparency weighting. overlay(fg, bg)   Estimates the resulting color that appears on the chart when placing one color over another. fromGradient(value, bottomValue, topValue, bottomColor, topColor, colorSpace)   Calculates the gradient color that corresponds to a specific value based on a defined value range and color space. fromMultiStepGradient(value, steps, colors, colorSpace)   Calculates a multi-step gradient color that corresponds to a specific value based on an array of step points, an array of corresponding colors, and a color space. gradientPalette(baseColor, stopColor, steps, strength, model)   Generates a palette from a gradient between two base colors. monoPalette(baseColor, grayLuminance, variations, strength, colorSpace)   Generates a monochromatic palette from a specified base color. harmonyPalette(baseColor, harmonyType, grayLuminance, variations, strength, colorSpace)   Generates a palette consisting of harmonious base colors and their monochromatic variants.
ספריית Pine Script®
מאת ‎TradingView‎
3
Multi-Indicator Signals with Selectable Options by DiGetMulti-Indicator Signals with Selectable Options Script Overview This Pine Script is a multi-indicator trading strategy designed to generate buy/sell signals based on combinations of popular technical indicators: RSI (Relative Strength Index) , CCI (Commodity Channel Index) , and Stochastic Oscillator . The script allows you to select which combination of signals to display, making it highly customizable and adaptable to different trading styles. The primary goal of this script is to provide clear and actionable entry/exit points by visualizing buy/sell signals with arrows , labels , and vertical lines directly on the chart. It also includes input validation, dynamic signal plotting, and clutter-free line management to ensure a clean and professional user experience. Key Features 1. Customizable Signal Types You can choose from five signal types: RSI & CCI : Combines RSI and CCI signals for confirmation. RSI & Stochastic : Combines RSI and Stochastic signals. CCI & Stochastic : Combines CCI and Stochastic signals. RSI & CCI & Stochastic : Requires all three indicators to align for a signal. All Signals : Displays individual signals from each indicator separately. This flexibility allows you to test and use the combination that works best for your trading strategy. 2. Clear Buy/Sell Indicators Arrows : Buy signals are marked with upward arrows (green/lime/yellow) below the candles, while sell signals are marked with downward arrows (red/fuchsia/gray) above the candles. Labels : Each signal is accompanied by a label ("BUY" or "SELL") near the arrow for clarity. Vertical Lines : A vertical line is drawn at the exact bar where the signal occurs, extending from the low to the high of the candle. This ensures you can pinpoint the exact entry point without ambiguity. 3. Dynamic Overbought/Oversold Levels You can customize the overbought and oversold levels for each indicator: RSI: Default values are 70 (overbought) and 30 (oversold). CCI: Default values are +100 (overbought) and -100 (oversold). Stochastic: Default values are 80 (overbought) and 20 (oversold). These levels can be adjusted to suit your trading preferences or market conditions. 4. Input Validation The script includes built-in validation to ensure that oversold levels are always lower than overbought levels for each indicator. If the inputs are invalid, an error message will appear, preventing incorrect configurations. 5. Clean Chart Design To avoid clutter, the script dynamically manages vertical lines: Only the most recent 50 buy/sell lines are displayed. Older lines are automatically deleted to keep the chart clean. Labels and arrows are placed strategically to avoid overlapping with candles. 6. ATR-Based Offset The vertical lines and labels are offset using the Average True Range (ATR) to ensure they don’t overlap with the price action. This makes the signals easier to see, especially during volatile market conditions. 7. Scalable and Professional The script uses arrays to manage multiple vertical lines, ensuring scalability and performance even when many signals are generated. It adheres to Pine Script v6 standards, ensuring compatibility and reliability. How It Works Indicator Calculations : The script calculates the values of RSI, CCI, and Stochastic Oscillator based on user-defined lengths and smoothing parameters. It then checks for crossover/crossunder conditions relative to the overbought/oversold levels to generate individual signals. Combined Signals : Depending on the selected signal type, the script combines the individual signals logically: For example, a "RSI & CCI" buy signal requires both RSI and CCI to cross into their respective oversold zones simultaneously. Signal Plotting : When a signal is generated, the script: Plots an arrow (upward for buy, downward for sell) at the corresponding bar. Adds a label ("BUY" or "SELL") near the arrow for clarity. Draws a vertical line extending from the low to the high of the candle to mark the exact entry point. Line Management : To prevent clutter, the script stores up to 50 vertical lines in arrays (buy_lines and sell_lines). Older lines are automatically deleted when the limit is exceeded. Why Use This Script? Versatility : Whether you're a scalper, swing trader, or long-term investor, this script can be tailored to your needs by selecting the appropriate signal type and adjusting the indicator parameters. Clarity : The combination of arrows, labels, and vertical lines ensures that signals are easy to spot and interpret, even in fast-moving markets. Customization : With adjustable overbought/oversold levels and multiple signal options, you can fine-tune the script to match your trading strategy. Professional Design : The script avoids clutter by limiting the number of lines displayed and using ATR-based offsets for better visibility. How to Use This Script Add the Script to Your Chart : Copy and paste the script into the Pine Editor in TradingView. Save and add it to your chart. Select Signal Type : Use the "Signal Type" dropdown menu to choose the combination of indicators you want to use. Adjust Parameters : Customize the lengths of RSI, CCI, and Stochastic, as well as their overbought/oversold levels, to match your trading preferences. Interpret Signals : Look for green arrows and "BUY" labels for buy signals, and red arrows and "SELL" labels for sell signals. Vertical lines will help you identify the exact bar where the signal occurred. Tips for Traders Backtest Thoroughly : Before using this script in live trading, backtest it on historical data to ensure it aligns with your strategy. Combine with Other Tools : While this script provides reliable signals, consider combining it with other tools like support/resistance levels or volume analysis for additional confirmation. Avoid Overloading the Chart : If you notice too many signals, try tightening the overbought/oversold levels or switching to a combined signal type (e.g., "RSI & CCI & Stochastic") for fewer but higher-confidence signals.
אינדיקטור Pine Script®
מאת ‎mikailhs‎
9
display_valueOVERVIEW This script is a tinny library for creating and displaying formatted values in TradingView scripts. It provides a structured way to present key information like titles, percentages, currency values, decimals, and integers with clear formatting. This allows you to coordinate your strings in advance and hold one item to use for calling your string to a label, box, table.. Made for day to day use of most typical use cases, more advanced techniques should be used for complicated scenarios. Building Blocks User Defined Types (UDTs) The script defines a UDT called `DisplayValue` to encapsulate the components of a display value:  * title : The title or label of the value.  * format_string : The string used to format the value (e.g., "{0} -     1,number,percent}").  * value : The actual value to be displayed.  * format : An enum value specifying the desired format (percent, currency, etc.). Enums The `DisplayFormat` enum provides predefined constants for various formatting options, making the code more readable and less prone to errors. Functions  * create() : This function creates a new `DisplayValue` instance. It takes the title, value, and desired format as arguments and generates the appropriate format string.  * to_string() : This function converts a `DisplayValue` instance into a formatted string ready for display on the chart. How to Use 1. Import the library: import kaigouthro/display_value/1as dv 2. Create a DisplayValue instance: myValue = dv.create("My Percentage", 0.5, dv.DisplayFormat.percent) 3. Convert it to a string: formattedString = dv.to_string(myValue) 4. Display the formatted string: label.new(bar_index, high, formattedString) Example //@version=5 import kaigouthro/display_value/1 as dv myValue = dv.create("Profit", 0.15, dv.DisplayFormat.percent) formattedString = dv.to_string(myValue) label.new(bar_index, high, formattedString) This will display a label on the chart with the text "Profit - 15%". ### Notes * The library handles the formatting details, making it easier to display values consistently in your scripts. * The use of enums and UDTs improves code organization and readability. -------- Library "display_value" create(display_name, display_value, display_format)   Gets the appropriate format string based on the display format.   Parameters:      display_name (string) : (string) The name of the display value. Default is na.      display_value (float)      display_format (series DisplayFormat)   Returns: (DisplayValue) A new DisplayValue instance with the formatted value. to_string(item)   Converts the display value to a string with the specified format.   Parameters:      item (DisplayValue) : (DisplayValue) The display value to convert to a string.   Returns: (string) The string representation of the display value. DisplayValue   Structure representing a display value.   Fields:      title (series string) : (string) The title of the display value.      format_string (series string) : (string) The format string to use for display.      value (series float) : (float) The value to display.      format (series DisplayFormat) : (DisplayFormat) The format to use.
ספריית Pine Script®
מאת ‎kaigouthro‎
Optimal Buy Day (Zeiierman)█ Overview The Optimal Buy Day (Zeiierman) indicator identifies optimal buying days based on historical price data, starting from a user-defined year. It simulates investing a fixed initial capital and making regular monthly contributions. The unique aspect of this indicator involves comparing systematic investment on specific days of the month against a randomized buying day each month, aiming to analyze which method might yield more shares or a better average price over time. By visualizing the potential outcomes of systematic versus randomized buying, traders can better understand the impact of market timing and how regular investments might accumulate over time. These statistics are pivotal for traders and investors using the script to analyze historical performance and strategize future investments. By understanding which days offered more shares for their money or lower average prices, investors can tailor their buying strategies to potentially enhance returns. █ Key Statistics ⚪ Shares Definition: Represents the total number of shares acquired on a particular day of the month across the entire simulation period. How It Works: The script calculates how many shares can be bought each day, given the available capital or monthly contribution. This calculation takes into account the day's opening price and accumulates the total shares bought on that day over the simulation period. Interpretation: A higher number of shares indicates that the day consistently offered better buying opportunities, allowing the investor to acquire more shares for the same amount of money. This metric is crucial for understanding which days historically provided more value. ⚪ AVG Price Definition: The average price paid per share on a particular day of the month, averaged over the simulation period. How It Works: Each time shares are bought, the script calculates the average price per share, factoring in the new shares purchased at the current price. This average evolves over time as more shares are bought at varying prices. Interpretation: The average price gives insight into the cost efficiency of buying shares on specific days. A lower average price suggests that buying on that day has historically led to better pricing, making it a potentially more attractive investment strategy. ⚪ Buys Definition: The total number of transactions or buys executed on a particular day of the month throughout the simulation. How It Works: This metric increments each time shares are bought on a specific day, providing a count of all buying actions taken. Interpretation: The number of buys indicates the frequency of investment opportunities. A higher count could mean more consistent opportunities for investment, but it's important to consider this in conjunction with the average price and the total shares acquired to assess overall strategy effectiveness. ⚪ Most Shares Definition: Identifies the day of the month on which the highest number of shares were bought, highlighting the specific day and the total shares acquired. How It Works: After simulating purchases across all days of the month, the script identifies which day resulted in the highest total number of shares bought. Interpretation: This metric points out the most opportune day for volume buying. It suggests that historically, this day provided conditions that allowed for maximizing the quantity of shares purchased, potentially due to lower prices or other factors. ⚪ Best Price Definition: Highlights the day of the month that offered the lowest average price per share, indicating both the day and the price. How It Works: The script calculates the average price per share for each day and identifies the day with the lowest average. Interpretation: This metric is key for investors looking to minimize costs. The best price day suggests that historically, buying on this day led to acquiring shares at a more favorable average price, potentially maximizing long-term investment returns. ⚪ Randomized Shares Definition: This metric represents the total number of shares acquired on a randomly selected day of the month, simulated across the entire period. How It Works: At the beginning of each month within the simulation, the script selects a random day when the market is open and calculates how many shares can be purchased with the available capital or monthly contribution at that day's opening price. This process is repeated each month, and the total number of shares acquired through these random purchases is tallied. Interpretation: Randomized shares offer a comparison point to systematic buying strategies. By comparing the total shares acquired through random selection against those bought on the best or worst days, investors can gauge the impact of timing and market fluctuations on their investment strategy. A higher total in randomized shares might indicate that over the long term, the specific days chosen for investment might matter less than consistent market participation. Conversely, if systematic strategies yield significantly more shares, it suggests that timing could indeed play a crucial role in maximizing investment returns. ⚪ Randomized Price Definition: The average price paid per share for the shares acquired on the randomly selected days throughout the simulation period. How It Works: Each time shares are bought on a randomly chosen day, the script calculates the average price paid for all shares bought through this randomized strategy. This average price is updated as the simulation progresses, reflecting the cost efficiency of random buying decisions. Interpretation: The randomized price metric helps investors understand the cost implications of a non-systematic, random investment approach. Comparing this average price to those achieved through more deliberate, systematic strategies can reveal whether consistent investment timing strategies outperform random investment actions in terms of cost efficiency. A lower randomized price suggests that random buying might not necessarily result in higher costs, while a higher average price indicates that systematic strategies might provide better control over investment costs. █ How to Use Traders can use this tool to analyze historical data and simulate different investment strategies. By inputting their initial capital, regular contribution amount, and start year, they can visually assess which days might have been more advantageous for buying, based on historical price actions. This can inform future investment decisions, especially for those employing dollar-cost averaging strategies or looking to optimize entry points. █ Settings StartYear: This setting allows the user to specify the starting year for the investment simulation. Changing this value will either extend or shorten the period over which the simulation is run. If a user increases the value, the simulation begins later and covers a shorter historical period; decreasing the value starts the simulation earlier, encompassing a longer time frame. Capital: Determines the initial amount of capital with which the simulation begins. Increasing this value simulates starting with more capital, which can affect the number of shares that can be initially bought. Decreasing this value simulates starting with less capital. Contribution: Sets the monthly financial contribution added to the investment within the simulation. A higher contribution increases the investment each month and could lead to more shares being purchased over time. Lowering the contribution decreases the monthly investment amount. ----------------- Disclaimer The information contained in my Scripts/Indicators/Ideas/Algos/Systems does not constitute financial advice or a solicitation to buy or sell any securities of any type. I will not accept liability for any loss or damage, including without limitation any loss of profit, which may arise directly or indirectly from the use of or reliance on such information. All investments involve risk, and the past performance of a security, industry, sector, market, financial product, trading strategy, backtest, or individual's trading does not guarantee future results or returns. Investors are fully responsible for any investment decisions they make. Such decisions should be based solely on an evaluation of their financial circumstances, investment objectives, risk tolerance, and liquidity needs. My Scripts/Indicators/Ideas/Algos/Systems are only for educational purposes!
אינדיקטור Pine Script®
מאת ‎Zeiierman‎
3
No Wick Bull/Bear Candlesticks with Arrow premiumNo Wick Bull/Bear Candlesticks with Arrow premium This script is for a custom trading indicator called "No Wick Bull/Bear Candlesticks with Arrow premium" developed by ClearTradingMind. It is designed for use with trading platforms that support scripting, such as TradingView. This indicator combines several technical analysis tools to help traders identify potential buy and sell signals in a financial market. Key Components of the Indicator: Moving Average (MA): The script allows users to select from various types of moving averages (SMA, EMA, HMA, etc.), which smooth out price data to identify trends. Users can set the length and type of the moving average. Upper and Lower Bands: These bands are set at a specified deviation percentage above and below the chosen moving average. They help in identifying overbought and oversold conditions. No Wick Bull/Bear Candlestick Identification: Bullish Condition: A bullish candlestick is identified when the closing price is higher than the opening price, the low equals the open, and the close is above the moving average. Bearish Condition: A bearish candlestick is identified when the closing price is lower than the opening price, the high equals the open, and the close is below the moving average. No Wick: These conditions also imply that the candlesticks have no wicks, suggesting strong buying or selling pressure. Arrows for Trading Signals: No lower wick bull bar No upper wick bear bar When a bullish condition is met, a green upward-pointing triangle is plotted below the candlestick, indicating a potential buy signal. When a bearish condition is met, a red downward-pointing triangle is plotted above the candlestick, indicating a potential sell signal. EMA 20: An additional Exponential Moving Average with a length of 20 periods is plotted for further trend analysis. Background Color Changes: The script changes the background color to blue if the EMA 20 is above the upper band, and to red if it is below the lower band, providing visual cues about the market trend. How It Works: Traders can input their preferences for the moving average type and length, source of the MA (like closing prices), and the deviation percentage for the bands. The script then calculates the moving average, upper and lower bands, and checks for bullish or bearish candlestick conditions without wicks. When such conditions are met, it plots arrows to suggest buy or sell signals. The EMA 20 and background color changes offer additional trend information. Usage: This indicator is particularly useful in markets with clear trends. The no wick bull/bear candlesticks indicate strong buying or selling pressure, and the arrows provide clear visual signals for traders to consider entering or exiting positions. As with all trading indicators, it's recommended to use this tool in conjunction with other forms of analysis to confirm trading signals.
אינדיקטור Pine Script®
מאת ‎ClearTradingMind‎
1
Liquidation Ranges + Volume/OI Dots [Kioseff Trading]Hello! Introducing a multi-faceted indicator "Liquidation Ranges + Volume Dots" - this indicator replicates the volume dot tools found on various charting platforms and populates a liquidation range on crypto assets! Features Volume/OI dots populated according to user settings Size of volume/OI dots corresponds to degree of abnormality Naked level volume dots Fixed range capabilities for volume/OI dots Visible time range capabilities for volume/OI dots Lower timeframe data used to discover iceberg orders (estimated using 1-minute data) S/R lines drawn at high volume/OI areas Liquidation ranges for crypto assets (10x - 100x) Liquidation ranges are calculated using a popular crypto exchange's method # of violations of liquidation ranges are recorded and presented in table Pertinent high volume/OI price areas are recorded and presented in table Personalized coloring for volume/OI dots Net shorts / net long for the price range recorded Lines shows reflecting net short & net long increases/decreases Configurable volume/OI heatmap (displayed between liquidation ranges) And some more (: Liquidation Range The liquidation range component of the indicator uses a popular crypto exchange's calculation (for liquidation ranges) to populate the chart for where 10x - 100x leverage orders are stopped out. The image above depicts features corresponding to net shorts and net longs. The image above shows features corresponding to liquidation zones for the underlying coin. The image above shows the option to display volume/oi delta at the time the corresponding grid was traded at. The image above shows an instance of using the "fixed range" feature for the script. *The average price of the range is calculated to project liquidation zones. *Heatmap is calculated using OI (or volume) delta. Huge thank you to Pine Wizard @DonovanWall for his range filter code! Price ranges are automatically detected using his calculation (: Volume / OI Dots Similar to other charting platforms, the volume/OI dots component of the indicator distinguishes "abnormal" changes in volume/OI; the detected price area is subsequently identified on the chart. The detection method uses percent rank and calculates on the last bar of the chart. The "agelessness" of detection is contingent on user settings. The image above shows volume dots in action; the size of each volume dot corresponds to the amount of volume at the price area. Smaller dots = lower volume Larger dots = higher volume The image above exemplifies the highest aggression setting for volume/OI dot detection. The table oriented top-right shows the highest volume areas (discovered on the 1-minute chart) for the calculated period. The open interest change and corresponding price level are also shown. Results are listed in descending order but can also be listed in order of occurrence (most relevant). Additionally, you can use the visible time range feature to detect volume dots. The feature shows and explains how the visible range feature works. You select how many levels you want to detect and the script will detect the selected number of levels. For instance, if I select to show 20 levels, the script will find the 20 highest volume/OI change price areas and distinguish them. The image above shows a narrower price range. The image above shows the same price range; however, the script is detecting the highest OI change price areas instead of volume. * You can also set a fixed range with this feature * Naked levels can be used Additionally, you can select for the script to show only the highest volume/ OI change price area for each bar. When active, the script will successively identify the highest volume / OI change price area for the most recent bars. Naked Levels The image above shows and explains how naked levels can be detected when using the script. And that's pretty much it! Of course, there're a few more features you can check out when you use the script that haven't been explained here (: Thank you again to @DonovanWall Thank you to @Trendoscope for his binary insertion sort library (: Thank you to @PineCoders for their time library Thank you for checking this out!
אינדיקטור Pine Script®
מאת ‎KioseffTrading‎
61
Reversal Signals [LuxAlgo]The Reversal Signals indicator is a technical analysis tool that aims to identify when a trend is fading and potentially starting to reverse. As a counter-trend tool, the Reversal Signals indicator aims to solve the problem of several technical analysis indicators that perform well during trending markets but struggle in ranging markets. By understanding the key concepts and applications of the tool, traders can enhance their market timing and improve their trading strategies. Note: It's important to explore the settings of the indicator to customize to your own usage & display as there are various options available as covered below. 🔶 USAGE The Reversal Signals indicator is comprised of two main phases: Momentum Phase and Trend Exhaustion Phase . These phases help identify potential trend reversals in bullish, bearish, and ranging markets. 🔹The Momentum Phase The momentum phase consists of a 9-candle count and in rare cases 8-candle count. In a bullish trend, a starting number ‘1’ is plotted if a candle closes higher than the close of a candle four periods ago. In a bearish trend, a starting number ‘1’ is plotted if a candle closes lower than the close of a candle four periods ago. The following numbers are plotted when each successive candle satisfies the four-period rule. The potential reversal point comes when the Reversal Signals plot a label on top of a candle in a bullish trend or at the bottom of a candle in a bearish trend. The momentum phase is immediately canceled if, at any point, a candle fails to satisfy the four-period rule. Based on the extremes of the momentum phase, the Reversal Signals generate support & resistance levels as well as risk/stop levels. 🔹 The Trend Exhaustion Phase The trend exhaustion phase starts after completing the momentum phase and consists of a 13-candle count. In a bullish trend exhaustion phase, each candle’s close is compared to the close of two candles earlier, and the close must be greater than the close two periods earlier. In a bearish trend exhaustion phase, each candle’s close is compared to the close of two candles earlier, and the close must be lower than the close two periods earlier. The trend exhaustion phase does not require a consecutive sequence of candles; if the order of candles is interrupted, the trend exhaustion phase is not canceled. The trend exhaustion phase generates stronger trading signals than the momentum phase, with the potential for longer-lasting price reversals. 🔹 Trading Signals The Reversal Signals script presents an overall setup and some phase-specific trade setup options, where probable trades might be considered. All phase-specific trade setups, presented as options, are triggered once the selected phase is completed and followed by a price flip in the direction of the trade setup. Please note that those setups are presented for educational purposes only and do not constitutes professional and/or financial advice - Momentum: Enter a trade at momentum phase completion, and search for buy (sell) when the bullish (bearish) momentum phase pattern is complete. Ideally, the momentum phase completion should close near its support/resistance line but shall not be above them, which indicates continuation of the trend - Exhaustion: Enter a trade on trend exhaustion phase completion, and search for buy (sell) when the bullish (bearish) trend exhaustion phase is complete - Qualified: Buy (sell) when a bullish (bearish) trend exhaustion phase combined with another bullish (bearish) momentum phase sequence is complete Long trade setups are presented with "L" label and short trade setups with "S" label, where the content of the label displays details related to the probable trade opportunity Once a phase-specific trade setup is triggered then the Reversal Signals script keeps checking the status of the price action relative to the phase-specific trade setups and in case something goes wrong presents a caution label. Pay attention to the content of the caution labels as well as where they appear. A trade signal, followed immediately by a warning indication can be assumed as a continuation of the underlying trend and can be traded in the opposite direction of the suggested signal It is strongly advised to confirm trading setups in conjunction with other forms of technical and fundamental analysis, including technical indicators, chart/candlestick pattern analysis, etc. 🔶 DETAILS The Reversal Signals script performs the detection of the phases by counting the candlestick meeting the specific conditions, which includes: - Detection of the 8th and 9th candle perfection during the momentum phase - In some cases, the 8th count will be assumed as momentum phase completion - Trend exhaustion phase counting stops in case any type of momentum phase completion is detected during the counting process - Postponing the last count of the trend exhaustion phase, the 13th candle must be below/above the 8th candle and if not the candles will be indicated with '+' sign under them and the script continues to search for a 13th candle at the next ones until the conditions are met 🔶 ALERTS When an alert is configured, the user will have the ability to be notified in case; Momentum / Trend Exhaustion phase completion Support & Resistance level cross detection Stop / Risk level cross detection Long / Short Trade Setups are triggered Please note, alerts are available with 'any alert() function call' and the alerts will be received only for the features that are enabled during alert configuration 🔶 SETTINGS 🔹 Momentum Phase Display Phases: displays the momentum phases, where the Completed option allows the display of only completed momentum phases. The detailed option allows the display of the entire process of the momentum phase processes Support & Resistance Levels: Toggles the visibility of the Support & Resistance Levels and Line Styling options Momentum Phase Risk Levels: Toggles the visibility of the momentum phase Stop/Risk Levels and Line Styling options For color options please refer to the options available under the style tab 🔹 Trend Exhaustion Phase Display Phases: displays the trend exhaustion phases, where the Completed option allows the display of only completed trend exhaustion phases. The detailed option allows the display of the entire process of the trend exhaustion phase processes Trend Exhaustion Phase Risk Levels: Toggles the visibility of the trend exhaustion phase Stop/Risk Levels Trend Exhaustion Phase Target Levels: Toggles the visibility of the trend exhaustion phase Target Levels For color options please refer to the options available under the style tab 🔹 Trade Setups Overall Trend Direction & Trade Setup: displays the overall trend and probable trade setup levels, the users should search for a price flip and confirm with other means of technical and fundamental analysis for the trade setups once the label is plotted Phase-Specific Trade Setup Options Momentum: Searches for a trade setup after momentum phase completion Exhaustion: Searches for a trade setup after trend exhaustion phase completion, stronger trend reversal possibility compared to momentum phase setup Qualified: Searches for a trade setup after the trend exhaustion phase followed by a momentum phase completion None: No trade setups are presented Price Flips against the Phase Specific Trade Setups: enables checking the price action relative to the phase-specific trade setups 🔶 RELATED SCRIPTS Here are the scripts that may add additional insight during potential trading decisions. Buyside-Sellside-Liquidity Support-Resistance-Classification
אינדיקטור Pine Script®
מאת ‎LuxAlgo‎
60